Commiting from Azure Repos

[FinishingLine]

Seem to be struggling getting a commit working from Azure Repos (AR) to get this commited in Github (GH) - probably doing something stupid

From AR pipeline, I'm cloning the GH repo; moving files + directories that I need to keep; then adding files that have been generated with my AR pipeline process; then commiting it, adding a tag, then pushing it to GH

git clone https://%PAT%@github.com/xxx/yyy.git yyy

copy yyy\index.md docs\index.md /y

rmdir yyy /s /q

xcopy docs\subdir\* yyy\subdir\ /s /i /r /y
copy docs\index.md yyy\

cd yyy

git config user.email "[email protected]"
git config user.name "Service Account"

git add subdir

git commit -a -m "Docs Update"
git tag v%BUILDVERSION%
git push --force --tags --set-upstream https://%PAT%@github.com/xxx/yyy.git

Then within the GH action where hopefully it creates a branch to put the commit that comes through onto

on:
  push:
    tags:
      - 'v*'

name: Create Release

jobs:
  build:
    name: Create Release
    runs-on: ubuntu-latest
    permissions:
      pull-requests: write
      contents: write
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
          ref: ${{ github.head_ref }}
      - uses: stefanzweifel/git-auto-commit-action@v5
        with:
          branch: "docs/update"
          create_branch: true
          commit_message: "Docs Update"
          tagging_message: "${{ github.ref_name }}"
          push_options: '--force'

Everything seems to work fine, but keep getting the below

Working tree clean. Nothing to commit.

My guess is that the push isn't quite right or missing something in checkout? The files have 100% come across as I can see them under the tag within GH, complete with the changes - so not sure what needs tweaking

[stefanzweifel]

Hi there

I don't have experience with Azure Repos, but as far as I understand your code, you run your shell script on Azure Repos (?), make changes and push these changes to github.com.

Then on github.com, you have a workflow that listen when a new tag has been pushed to the repo.

In that workflow …

1. you clone the repository and it's entire history
2. immediately try to create a commit and push the commit to the GitHub repository

In between checkout and commit, the state of the repo does not change. You check out org/repository at v1.0.0 and tell git-auto-commit to switch to a docs/update.
But as no files actually change "Working tree clean. Nothing to commit." is shown.

(Here's the shell script that powers git-auto-commit)

---

Wouldn't it be easier to adjust your shell script also push to docs/update?

git clone https://%PAT%@github.com/xxx/yyy.git yyy

copy yyy\index.md docs\index.md /y

rmdir yyy /s /q

xcopy docs\subdir\* yyy\subdir\ /s /i /r /y
copy docs\index.md yyy\

cd yyy

git config user.email "[email protected]"
git config user.name "Service Account"

git add subdir

git commit -a -m "Docs Update"
git tag v%BUILDVERSION%
git push --force --tags --set-upstream https://%PAT%@github.com/xxx/yyy.git

# push to docs/update as well
git push --force --tags --set-upstream https://%PAT%@github.com/xxx/yyy.git origin "HEAD:docs/update"