Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QA: add reusable merge conflict check workflow #4

Merged
merged 1 commit into from
Dec 22, 2024

Conversation

jrfnl
Copy link
Contributor

@jrfnl jrfnl commented Dec 22, 2024

❗ This PR replaces PR #3

This commit introduces a new, reusable workflow to check if PRs are in a "conflict state", and if so, add a "merge conflict" label and leave a comment on the PR.

The workflow uses a pre-existing action runner which offers a number of options to configure the action.

While the workflow itself is pretty straight-forward, it has been set up as a reusable workflow to centrally manage the default option settings for all repos.

Individual calling workflows can still overrule these defaults for the most pertinent options.

For the less pertinent settings, this overload has not been enabled, but these options can still be opened up to calling workflows at a later point in time if there is a need for it.

It also adds a workflow to use the reusable action for this repo. Even though it is pretty unlikely there will be a multiple PRs open at the same time for this repo, running the action on each merge will provide some basic QA.

Refs:

This commit introduces a new, reusable workflow to check if PRs are in a "conflict state", and if so, add a "merge conflict" label and leave a comment on the PR.

The workflow uses a pre-existing action runner which offers a number of options to configure the action.

While the workflow itself is pretty straight-forward, it has been set up as a reusable workflow to centrally manage the default option settings for all repos.

Individual calling workflows can still overrule these defaults for the most pertinent options.

For the less pertinent settings, this overload has not been enabled, but these options can still be opened up to calling workflows at a later point in time if there is a need for it.

It also adds a workflow to use the reusable action for this repo.
Even though it is pretty unlikely there will be a multiple PRs open at the same time for this repo, running the action on each merge will provide some basic QA.

Refs:
* https://github.com/eps1lon/actions-label-merge-conflict
@jrfnl jrfnl merged commit 07dbec7 into main Dec 22, 2024
2 checks passed
@jrfnl jrfnl deleted the JRF/add-reusable-merge-conflict-check-workflow branch December 22, 2024 01:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant