Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: gitgitgadget/gitgitgadget-workflows
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: e5eeb9c
Choose a base ref
...
head repository: gitgitgadget/gitgitgadget-workflows
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: de0ba98
Choose a head ref
  • 6 commits
  • 7 files changed
  • 1 contributor

Commits on Sep 4, 2025

  1. sync-upstream-branches: configure the workflow via vars.CONFIG 

    The grand idea to use GitGitGadget for projects other than Git is to
allow configuring it via a custom JSON that is stored as a repository
variable.

Let's do this.

Signed-off-by: Johannes Schindelin <[email protected]>
    @dscho
    dscho committed Sep 4, 2025
    Configuration menu
    Copy the full SHA
    b1e6efc View commit details
    Browse the repository at this point in the history

  2. sync-mailing-list-mirror: configure the workflow via vars.CONFIG 

    The grand idea to use GitGitGadget for projects other than Git is to
allow configuring it via a custom JSON that is stored as a repository
variable.

Let's do this.

Signed-off-by: Johannes Schindelin <[email protected]>
    @dscho
    dscho committed Sep 4, 2025
    Configuration menu
    Copy the full SHA
    de82391 View commit details
    Browse the repository at this point in the history

  3. WIP (fill in TBD) Use vars.CONFIG with all of GitGitGadget's GitHub… 

    … Actions

The GitHub Actions of GitGitGadget just learned the trick to accept the
project configuration as an input parameter. The idea is to store this
configuration in the repository variable called `CONFIG`. Here is the
code change to make use of this repository variable.

Obviously, this means that the workflows should no longer run in forks
without said configuration.

For details about configuring GitGitGadget to support projects other
than Git, see TBD.

Signed-off-by: Johannes Schindelin <[email protected]>
    @dscho
    dscho committed Sep 4, 2025
    Configuration menu
    Copy the full SHA
    542bda4 View commit details
    Browse the repository at this point in the history

  4. Use more generic names for the -token steps 

    With my current push to let GitGitGadget work for other projects than
Git, it is no longer appropriate to refer to the `git` repository forks
directly.

Signed-off-by: Johannes Schindelin <[email protected]>
    @dscho
    dscho committed Sep 4, 2025
    Configuration menu
    Copy the full SHA
    146bf8d View commit details
    Browse the repository at this point in the history

  5. Use the {upstream,pr,test}-repo information from the repository config 

    We just started to pass the project-specific configuration stored in the
`CONFIG` repository variable to the GitHub Actions of GitGitGadget.

That configuration contains information about the correct repositories
to target (which might not be `gitgitgadget/git` and friends). Let's use
this information when obtaining (and using) the installation access
tokens.

This is especially necessary when creating and updating that Check Run
in `handle-pr-push` and in `handle-pr-comment`.

Signed-off-by: Johannes Schindelin <[email protected]>
    @dscho
    dscho committed Sep 4, 2025
    Configuration menu
    Copy the full SHA
    1d8eaa4 View commit details
    Browse the repository at this point in the history

  6. handle-pr-comment: stop hard-coding the SMTP user and host 

    These should be taken from the project config which is now expected to
be present as the `CONFIG` repository variable.

Signed-off-by: Johannes Schindelin <[email protected]>
    @dscho
    dscho committed Sep 4, 2025
    Configuration menu
    Copy the full SHA
    de0ba98 View commit details
    Browse the repository at this point in the history
Loading