You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rkeene: aku, One option is to have a "release" branch that corresponds to the contents of the release tarball that forks at the release point, then tag that commit on the release branch
aku: Oh. I see. Make a branch where the linenoise sources are in the repo, and thus automatically in the tarball github will create.
rkeene: Basically create the tarball, create the branch (can Git have multiple branches with the same name ?), then get rid of everything in the branch, and replace it with stuff in the tarball, tag that commit as the release
Note: The above dance gets around github's insistence that the "sources" of a release should be a tagged commit in the repository. They automatically link to the commit and auto-generate archives. The result normally is not a proper release with RE artifacts.
The text was updated successfully, but these errors were encountered:
Notes
From chat
Note: The above dance gets around github's insistence that the "sources" of a release should be a tagged commit in the repository. They automatically link to the commit and auto-generate archives. The result normally is not a proper release with RE artifacts.
The text was updated successfully, but these errors were encountered: