-
Notifications
You must be signed in to change notification settings - Fork 46
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
fix: do not push empty commits #2831
base: master
Are you sure you want to change the base?
Conversation
Hi @abitrolly. Thanks for your PR. I'm waiting for a jenkins-x or todo member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. |
/cc @rawlingsj |
I am not sure why we allowed empty commits in the first place? @rawlingsj any ideas? |
It was there from the first commit b226d96 Perhaps @jstrachan can remember. |
My guess is that it was done so that the release pipeline did not stop if there were issues with that step 🤷 |
Also, since it's a harmless change, best to keep it as it is, we can remove it, once we know the motivation behind it. |
By harmless change do you mean this PR? |
No, I meant allowing the empty changes, It's harmless and does not break anything, but changing this, might lead to issues down the line. Probably best to understand the full implications before making this change. |
/hold |
Not really harmless. I read it as a false alarm that a new version is released. Maybe I should stop looking for new versions. :D |
This PR is apparently abandoned |
@msvticket it is possible to resurrect, but it needs to be reopened. |
@msvticket committed your change. Hopefully that works as expected. :D |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: msvticket The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
Co-authored-by: Mårten Svantesson <[email protected]>
@abitrolly: The following test failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here. |
No description provided.