-
Notifications
You must be signed in to change notification settings - Fork 202
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
loosen commit message requirements w.r.t. to patches as long as all easyconfigs are new #2438
loosen commit message requirements w.r.t. to patches as long as all easyconfigs are new #2438
Conversation
@migueldiascosta This makes sense to me, I've found the current behaviour rather annoying and unnecessary myself... :) We need to be a bit careful when changing I'll run the |
No problems with tests, so this is good to go imho. Thanks @migueldiascosta! |
Ugh, seems like I wasn't careful enough, I didn't check the GitHub-related tests in @migueldiascosta Can you look into fixing this broken test?
|
…dding a patch following the change in PR easybuilders#2438
…dding a patch following the change in PR easybuilders#2438
broken test fixed in #2443 |
It seems to me that as long as all easyconfigs are new, the commit message could still be automatically generated
If a new patch being added applies to an existing easyconfig, that easyconfig would need to be modified so a meaningful commit message is still needed, this change only affects the cases where all easyconfig files are new
do close if I'm missing something