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

Automate upmerge PRs #931

Open
AaronCrawfis opened this issue Jan 11, 2024 · 0 comments
Open

Automate upmerge PRs #931

AaronCrawfis opened this issue Jan 11, 2024 · 0 comments
Labels
maintenance Issue is a non-user-facing task like updating tests, improving automation, etc.. triaged This item has been triaged by project maintainers and is in the backlog

Comments

@AaronCrawfis
Copy link
Contributor

AaronCrawfis commented Jan 11, 2024

Today we have a manual process to "upmerge", or create a PR with all the changes, from the most recent versioned branch into the edge branch.

The reason we do this is because we want improvements to the samples to go into the versioned branch instead of into edge, so that end users don't have to wait a month to get the updates as part of the next release.

We need an automated process for this though, as the manual process is frequently forgotten.

We should:

  1. Create a GitHub workflow that runs every Friday morning to create a PR from the default branch into the edge branch.
  2. Add a workflow_dispatch trigger as well so it can be run manually if there's something important that needs to be upmerged

AB#10876

@shalabhms shalabhms added triaged This item has been triaged by project maintainers and is in the backlog maintenance Issue is a non-user-facing task like updating tests, improving automation, etc.. labels Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Issue is a non-user-facing task like updating tests, improving automation, etc.. triaged This item has been triaged by project maintainers and is in the backlog
Projects
None yet
Development

No branches or pull requests

2 participants