-
Notifications
You must be signed in to change notification settings - Fork 1
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
SRVLOGIC-202: Schedule apache-main sync from upstream #3
SRVLOGIC-202: Schedule apache-main sync from upstream #3
Conversation
Review request: @ricardozanini @rgdoliveira |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it looks good too.
@fantonangeli @ricardozanini I suppose we can merge this one and see it working and after that @fantonangeli can open this PR to the other repositories, WDYT?
@ricardozanini @rgdoliveira |
@fantonangeli I guess you have permissions to change the default branch to |
I confirm I have the permissions, I can do it right now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Done. |
Jira:
https://issues.redhat.com/browse/SRVLOGIC-202
IMPORTANT:
Please read the jira comments.
Description of the change:
Set up a GitHub Action to sync our midstream main-apache branch with the upstream main branch every day.
This workflow will run every day at midnight to merge upstream/main to origin/main-apache.
The repository used to test this workflow is
fantonangeli/kogito-serverless-operator-fantonangeli-test
:https://github.com/fantonangeli/kogito-serverless-operator-fantonangeli-test/actions
Motivation for the change:
Keep our repository in sync with the upstream Apache repository.
Checklist
How to backport a pull request to a different branch?
In order to automatically create a backporting pull request please add one or more labels having the following format
backport-<branch-name>
, where<branch-name>
is the name of the branch where the pull request must be backported to (e.g.,backport-7.67.x
to backport the original PR to the7.67.x
branch).Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.