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

chore: update PR template to suggest cherry-pick releases #16560

Merged

Conversation

jessesuen
Copy link
Member

In today's community meeting, I proposed that the authors of PRs could suggest how far back a bug fix should be cherry-picked. This adds an item as part of the checklist.

This allows the author to advocate for a cherry-pick, since they are fixing the bug for a reason (it probably impacts them). The fix may or may not be backported depending on the risk/complexity of the fix, as well as the age of the release, as decided by maintainers.

I also rearranged the checklist to have optional stuff at the bottom.

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Toolchain Guide
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • Optional. My organization is added to USERS.md.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.

@jessesuen jessesuen requested review from a team as code owners December 6, 2023 18:58
@jessesuen
Copy link
Member Author

@ericblackburn - this is what I proposed in today's meeting

Copy link

codecov bot commented Dec 6, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (86f79ec) 49.48% compared to head (1e9f7c6) 49.49%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #16560   +/-   ##
=======================================
  Coverage   49.48%   49.49%           
=======================================
  Files         270      270           
  Lines       47489    47489           
=======================================
+ Hits        23502    23506    +4     
+ Misses      21675    21672    -3     
+ Partials     2312     2311    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@34fathombelow 34fathombelow left a comment

Choose a reason for hiding this comment

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

LGTM, thanks Jessie!

@crenshaw-dev crenshaw-dev enabled auto-merge (squash) December 6, 2023 19:14
@crenshaw-dev crenshaw-dev merged commit 710777e into argoproj:master Dec 6, 2023
25 checks passed
vladfr pushed a commit to vladfr/argo-cd that referenced this pull request Dec 13, 2023
tesla59 pushed a commit to tesla59/argo-cd that referenced this pull request Dec 16, 2023
JulienFuix pushed a commit to JulienFuix/argo-cd that referenced this pull request Feb 6, 2024
lyda pushed a commit to lyda/argo-cd that referenced this pull request Mar 28, 2024
Hariharasuthan99 pushed a commit to AmadeusITGroup/argo-cd that referenced this pull request Jun 16, 2024
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.

3 participants