-
Notifications
You must be signed in to change notification settings - Fork 82
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
typos #377
typos #377
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small but solid changes. 👌
Thank you for the tidying up, @a-detiste. o7 |
I've discovered a fault in my CI setup with regards to builds from forks: turns out only pull_request triggers from forks can fire, not push triggers. https://docs.github.com/en/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks This now needs to go first: #380 And then one can simply click the "update branch" button on this branch and reapprove and the automerge and merge queue machinery will take care of the rest. Sorry for the inconvenience. |
I plan to package this for Debian at the event that's happening end of this week in Cambridge. (FWIW) then we can update Frogatto. |
Please coordinate all things Debian with Martin Quinson as he seems to be the currently active uploader for the frogatto package. |
I never received the message that is publicly archived here: https://bugs.debian.org/1055343 I know now it's being handled, thanks for the tip. |
typo found by Debian's lintian