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

Automatically assign high priority items to project 25. #2213

Merged
merged 2 commits into from
Jan 25, 2024

Conversation

samsrabin
Copy link
Collaborator

@samsrabin samsrabin commented Oct 19, 2023

Description of changes

Adds a Github action to automatically assign high-priority items to Project 25: High priority.

Specific notes

Contributors other than yourself, if any: None

CTSM Issues Fixed (include github issue #): None

Are answers expected to change (and if so in what way)? No

Any User Interface Changes (namelist or namelist defaults changes)? No

Testing performed, if any: Doesn't seem to be working at the moment, but maybe that's just because it needs to be merged to the master branch.

@samsrabin samsrabin added the priority: high High priority to fix/merge soon, e.g., because it is a problem in important configurations label Oct 19, 2023
@samsrabin samsrabin added priority: high High priority to fix/merge soon, e.g., because it is a problem in important configurations and removed priority: high High priority to fix/merge soon, e.g., because it is a problem in important configurations labels Oct 19, 2023
@samsrabin
Copy link
Collaborator Author

Hmm. Seems to not be working.

@samsrabin samsrabin added priority: low Background task that doesn't need to be done right away. and removed priority: high High priority to fix/merge soon, e.g., because it is a problem in important configurations labels Oct 19, 2023
@samsrabin samsrabin self-assigned this Oct 19, 2023
@billsacks
Copy link
Member

This is great, @samsrabin (assuming you can get it to work) - thanks for doing this!

@samsrabin
Copy link
Collaborator Author

  • Fix.

@samsrabin samsrabin marked this pull request as draft November 29, 2023 18:00
@ekluzek
Copy link
Collaborator

ekluzek commented Jan 19, 2024

@samsrabin I think this has to come to master for it to work. I'm not completely sure on that, but since this doesn't affect other things I'm good on bringing this in so we can see if that's required.

@samsrabin
Copy link
Collaborator Author

That would make sense. Okay, I'll fill out the PR description and ask you for a review.

@samsrabin samsrabin marked this pull request as ready for review January 19, 2024 18:04
Copy link
Contributor

@slevis-lmwg slevis-lmwg left a comment

Choose a reason for hiding this comment

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

@billsacks and @ekluzek appear to agree that this is worth merging as is and finding out whether it works once it's merged.

@slevis-lmwg slevis-lmwg merged commit 5fa6ecb into master Jan 25, 2024
2 of 3 checks passed
@ekluzek ekluzek deleted the auto-high-priority branch February 12, 2024 20:19
@samsrabin samsrabin added simple bfb bit-for-bit labels Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bfb bit-for-bit priority: low Background task that doesn't need to be done right away.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants