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

fix: do not push empty commits #2831

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

abitrolly
Copy link

No description provided.

@jenkins-x-bot
Copy link
Contributor

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@ankitm123
Copy link
Member

/cc @rawlingsj

@ankitm123
Copy link
Member

I am not sure why we allowed empty commits in the first place? @rawlingsj any ideas?

@abitrolly
Copy link
Author

It was there from the first commit b226d96 Perhaps @jstrachan can remember.

@ankitm123
Copy link
Member

My guess is that it was done so that the release pipeline did not stop if there were issues with that step 🤷

@ankitm123
Copy link
Member

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.

@abitrolly
Copy link
Author

By harmless change do you mean this PR?

@ankitm123
Copy link
Member

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.

@ankitm123
Copy link
Member

/hold
putting on hold, till we know more about the initial idea around allowing empty commits ...

@abitrolly
Copy link
Author

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

@msvticket
Copy link
Member

This PR is apparently abandoned

@msvticket msvticket closed this Oct 12, 2024
@abitrolly
Copy link
Author

@msvticket it is possible to resurrect, but it needs to be reopened.

@msvticket msvticket reopened this Oct 15, 2024
@abitrolly
Copy link
Author

@msvticket committed your change. Hopefully that works as expected. :D

@jenkins-x-bot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@msvticket
Copy link
Member

/ok-to-test

@jenkins-x-bot
Copy link
Contributor

@abitrolly: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
gsm a6095d3 link /test gsm

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants