-
Notifications
You must be signed in to change notification settings - Fork 198
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
commit message support #162
Comments
There was a recent thread on this on ostree-list. Related to the git repo/URL, we did land #676 - though we haven't talked about showing that in the UI in any way. It does seem clear we should at least have the equivalent of the new ostree commit -F. |
In the short term, if anyone wants to use commit messages right now, you can hack it like this, by having rpm-ostree write the commit, then overwrite it but use the contents:
This general principle applies broadly - you can use rpm-ostree just to generate content, and then ostree tooling to manipulate/edit/promote it after. Concrete cmdline I just tested:
|
You can make the "rpm-ostree just generates content" even more explicit by using
|
OSTree has them, we should support people writing them for a few reasons.
One use case I see is it's very common to maintain metadata in a git repository, and it'd be nice to have that git repo URL + commit in the message.
The text was updated successfully, but these errors were encountered: