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.

Sign up for GitHub

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

Jump to bottom

Introduce backport GHA #8368

Merged
merged 1 commit into from
Feb 8, 2023
Merged

Introduce backport GHA #8368

merged 1 commit into from
Feb 8, 2023

Conversation

JanKrivanek
Copy link
Member

@JanKrivanek JanKrivanek commented Jan 30, 2023 •
edited
Loading

Context

Introduces backport GitHub action for automation-aided propagation of changes between branches.

usage:
comment
/backport to <target bracnh>
on PR that needs to be backported (ideally after merging). New PR will be created backporting to the requested branch.

@JanKrivanek JanKrivanek mentioned this pull request Jan 30, 2023
Merged
rainersigwald
rainersigwald reviewed Jan 30, 2023
View reviewed changes
Copy link
Member

@rainersigwald rainersigwald left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No objection to this, though it hasn't been needed much lately (I strongly prefer a merge-forward lifecycle even for patches).

We'll have to turn on Actions, though--ping me and I can do that.

rainersigwald
rainersigwald approved these changes Jan 30, 2023
View reviewed changes
Copy link
Member

@rainersigwald rainersigwald left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No objection to this, though it hasn't been needed much lately (I strongly prefer a merge-forward lifecycle even for patches).

We'll have to turn on Actions, though--ping me and I can do that.

@JanKrivanek
Copy link
Member Author

It's just a quick experiment :-)
We can allways get rid of this if it turns out not very helpful or not very used.

@JanKrivanek
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ladipro
Copy link
Member

ladipro commented Feb 6, 2023

Is it intentional to have the file under workflows\workflows as opposed to just workflows?

@JanKrivanek
Copy link
Member Author

Is it intentional to have the file under workflows\workflows as opposed to just workflows?

Thanks! - Good catch - copy&paste error :-)
Moving...

@JanKrivanek JanKrivanek added the merge-when-branch-open PRs that are approved, except that there is a problem that means we are not merging stuff right now. label Feb 7, 2023
@JaynieBai JaynieBai merged commit 03dae90 into dotnet:main Feb 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ladipro ladipro ladipro approved these changes

@rainersigwald rainersigwald rainersigwald approved these changes

Assignees
No one assigned
Labels
merge-when-branch-open PRs that are approved, except that there is a problem that means we are not merging stuff right now.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@JanKrivanek @ladipro @rainersigwald @JaynieBai