-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
Don't modify original file #61
Comments
GeorgesStavracas
added a commit
to GeorgesStavracas/flatpak-github-actions
that referenced
this issue
Nov 23, 2021
GeorgesStavracas
added a commit
to GeorgesStavracas/flatpak-github-actions
that referenced
this issue
Nov 23, 2021
GeorgesStavracas
added a commit
to GeorgesStavracas/flatpak-github-actions
that referenced
this issue
Nov 23, 2021
Store the modified manifest in another JSON or YML file in the same folder of the original file, but prefixed with 'flatpak-github-action-modified-'. Fixes flatpak#61
bilelmoussaoui
pushed a commit
that referenced
this issue
Nov 23, 2021
Store the modified manifest in another JSON or YML file in the same folder of the original file, but prefixed with 'flatpak-github-action-modified-'. Fixes #61
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recently I've been looking into publishing OBS Studio into Flathub directly, and I noticed that the Flatpak builds were generating version numbers with the
-modified
suffix. OBS generates these version numbers by runninggit describe --dirty="-modified"
.Turns out, this action modifies the original Flatpak manifest file regardless of any actual changes. I think it's probably better to save the modified Flatpak manifest in a separate file, and build from that, instead of modifying the original directly.
The text was updated successfully, but these errors were encountered: