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

Add the configuration file for merge flow #10257

Merged

Conversation

f-alizada
Copy link
Contributor

@f-alizada f-alizada commented Jun 18, 2024

Context

Onboarding new merge flow based on the github actions

Changes Made

Added configuration file the flow was copied from: https://github.com/dotnet/versions/blob/main/Maestro/subscriptions.json. Currently it will not be read or change any behaviour of the merge flow but will be used by the new workflow.

Testing

None -> it is not functionality related changes

Notes

The flow from vs17.7 to vs17.8 was not added to the new configuration since the sdk 7 release has reached end of life.

FYI: @pavelsavara , @mmitche

@pavelsavara
Copy link
Member

@f-alizada I think you could also add the actual workflow trigger to main branch, because next time a release branch would be branched, the workflow trigger file would be already there.

@f-alizada
Copy link
Contributor Author

@f-alizada I think you could also add the actual workflow trigger to main branch, because next time a release branch would be branched, the workflow trigger file would be already there.

This is good, however I would like to bring this file from the merge flow => we will not see any conflicting files from the latest release -> main.

@f-alizada f-alizada merged commit e1ff6dc into dotnet:main Jun 20, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants