Skip to content

Commit

Permalink
release-git(pacman-packages): do support the new Pacman repository
Browse files Browse the repository at this point in the history
In git-for-windows/build-extra#595, I started
the official transition of Git for Windows' Pacman repository away from
an Azure Blob container in my personal account to
https://github.com/git-for-windows/pacman-repo.

For the transition period, this still requires the token to upload to
the Azure Blob container, but it also already requires credentials to
push to `pacman-repo`, in particular some committer information.

The `pacman-packages` job of the `release-git` workflow still needed
this, as I forgot to do this as part of 2d0492
(build-and-deploy/release-git: support the new Pacman repository,
2025-02-17).

Signed-off-by: Johannes Schindelin <[email protected]>
  • Loading branch information
dscho committed Feb 26, 2025
1 parent 20850d1 commit a729d78
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion .github/actions/pacman-packages/action.yml
Original file line number Diff line number Diff line change
Expand Up @@ -114,10 +114,14 @@ runs:
shell: bash
env:
GPG_OPTIONS: "--batch --yes --no-tty --list-options no-show-photos --verify-options no-show-photos --pinentry-mode loopback"
GPGKEY: ${{ inputs.gpg-key }}
run: |
mkdir -p "$HOME" &&
echo '${{ inputs.priv-gpg-key }}' | tr % '\n' | gpg $GPG_OPTIONS --import &&
git config --global gpg.program "$RUNNER_TEMP/build-extra/gnupg-with-gpgkey.sh"
git config --global gpg.program "$RUNNER_TEMP/build-extra/gnupg-with-gpgkey.sh" &&
info="$(gpg --list-keys --with-colons "${GPGKEY%% *}" | cut -d : -f 1,10 | sed -n '/^uid/{s|uid:||p;q}')" &&
git config --global user.name "${info% <*}" &&
git config --global user.email "<${info#*<}"
- uses: actions/create-github-app-token@v1
id: pacman-repo-token
with:
Expand Down

0 comments on commit a729d78

Please sign in to comment.