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

update release-plan CI jobs #636

Merged
merged 1 commit into from
Sep 16, 2024
Merged

update release-plan CI jobs #636

merged 1 commit into from
Sep 16, 2024

Conversation

mansona
Copy link
Member

@mansona mansona commented Sep 16, 2024

This fixes an issue where adding a label to a PR from a fork after it has been merged doesn't allow the release-plan job to run correctly

cc @simonihmig I noticed you had this exact issue with #623

@simonihmig
Copy link
Contributor

Wow, yes, this was super quick, how even @mansona? 😅

Thank you!

Copy link
Contributor

@simonihmig simonihmig left a comment

Choose a reason for hiding this comment

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

@mansona
Copy link
Member Author

mansona commented Sep 16, 2024

I mean maybe 🤷. I wouldn't ever try to update these things manually, I just ran npm init release-plan-setup@latest and it updated our setup to what we recommend people use. It is an idempotent command so if you ever want to update a repo then run that 👍 (and review the diff because there might be some customisations)

@mansona mansona merged commit 091f6a8 into main Sep 16, 2024
156 checks passed
@mansona mansona deleted the update-release-plan-more branch September 16, 2024 10:05
@github-actions github-actions bot mentioned this pull request Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants