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.

Sign up for GitHub

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

Jump to bottom

Bug: onyo new generates commit message new [1]: None (sometimes) #739

Open
TobiasKadelka opened this issue Dec 12, 2024 · 0 comments · May be fixed by #738
Open

Bug: onyo new generates commit message new [1]: None (sometimes) #739

TobiasKadelka opened this issue Dec 12, 2024 · 0 comments · May be fixed by #738
Assignees
@bpoldrack

Comments

@TobiasKadelka
Copy link
Collaborator

While looking into our inventory repository, I noticed that the last three calls of onyo new generated the incorrect commit message header new [1]: None. Previous commits were all still creating the expected message header, so there was probably some change introduced in the recent PRs.

Ben seems to have identified the cause and verified: "Confirmed. master is broken."
@bpoldrack bpoldrack self-assigned this Dec 17, 2024
@bpoldrack bpoldrack linked a pull request Dec 17, 2024 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bpoldrack bpoldrack

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Pseudo-Keys Part II: history metadata bpoldrack/onyo
2 participants
@bpoldrack @TobiasKadelka