Publish the GitHub Actions to a separate branch#1983
Merged
dscho merged 1 commit intomaingitgitgadget/gitgitgadget:mainfrom Aug 27, 2025
publish-github-actionsgitgitgadget/gitgitgadget:publish-github-actionsCopy head branch name to clipboard
Merged
Publish the GitHub Actions to a separate branch#1983dscho merged 1 commit intomaingitgitgadget/gitgitgadget:mainfrom publish-github-actionsgitgitgadget/gitgitgadget:publish-github-actionsCopy head branch name to clipboard
dscho merged 1 commit intomaingitgitgadget/gitgitgadget:mainfrom
publish-github-actionsgitgitgadget/gitgitgadget:publish-github-actionsCopy head branch name to clipboard
Conversation
This was referenced Aug 20, 2025
8a675e5 to
ac31502
Compare
Contributor
|
I have finished reviewing. Not entirely sure about the inclusion in the same repo but it keeps the dist build tied to the source. |
ac31502 to
28f50c4
Compare
Member
Author
|
Sorry for changing the base branch and then changing it back again; This was needed because GitHub still fails to handle stacked PRs incorrectly when a PR in the stack is merged (the dependent PRs will still show the now-already-merged commits as part of the PR, unless a stunt like changing the base branch away and back again is performed). |
webstech
reviewed
Aug 27, 2025
We converted GitGitGadget into a bunch of GitHub Actions. The core logic of these is implemented in Typescript, which means that the code needs to be transpiled and bundled before it can be used as GitHub Action. This new workflow does exactly that. It maintains a new branch, called `v1`, and incremental tags of the `v1` tip commits, that are updated whenever the `main` branch advances. The updates consist of merging in `main`'s commit history, but the actual tree contents reflect the transpiled output, ready to be called as a GitHub Action from GitHub workflows. To reduce bandwidth when using the Action, all source code is removed from these tip commits, except for the few resources (`WELCOME.md` and two shell scripts) that are moved into the location where they need to be in order to be picked up by the GitHub Actions whenever needed. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
28f50c4 to
c05d284
Compare
webstech
approved these changes
Aug 27, 2025
github-actions bot
pushed a commit
that referenced
this pull request
Aug 27, 2025
…lish-github-actions, 2025-08-27))
github-actions bot
pushed a commit
to Bassamx93/gitgitgadget
that referenced
this pull request
Aug 27, 2025
…itgadget/publish-github-actions, 2025-08-27))
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is part 4 (the final part in this repository) of addressing #609, and it is stacked on top of #1980, #1981, and #1982 (and therefore contains also the commits of those PRs), therefore I will leave this in draft mode until those PRs are merged.
After laying the groundwork for, and implementing, the set of GitHub Actions that can perform the same job as GitGitGadget's current Azure Pipelines can perform, this here PR adds automation to
CIHelperclass (together with its dependencies) from Typescript to JavaScript,dist/index.js,WELCOME.md, some shell scripts) into the location expected by thatdist/index.js,*/action.yml,*/index.js),v1branch (creating it as needed),v1.<running-number>,v1branch and the tag.The result of this is that GitGitGadget can still be developed conveniently in this here repository, and whenever anything gets merged to the
mainbranch, thev1branch is automatically updated so that it will be picked up by GitHub workflows containing statements like:That way, we finally address the fragile nature of the current setup where a set of Azure Pipelines maintain their own clone of
gitgitgadget/gitgitgadget, and having to runnpm ci && npm run buildas needed.This closes #1759