-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: Unstaged Changes #80
Comments
Can you share the action that you are using? Also the |
I had set This isn't confirmed, but I did run a ❌ I tried forking the branch and retrying -- didn't work. |
Could you show the |
|
And the action configuration? |
Here are the logs:
|
Also the action's |
name: Bump Package Version
on:
push:
branches:
- main
- master
permissions:
contents: write
jobs:
bump-version:
if: "!startsWith(github.event.head_commit.message, 'bump:')"
runs-on: ubuntu-latest
name: "Bump version and create changelog with commitizen"
steps:
- name: Check out Repo
uses: actions/checkout@v4
with:
token: "${{ secrets.GH_PAT }}"
fetch-depth: 0
- name: Commit changes
run: |
git status
- name: Create bump and changelog
uses: commitizen-tools/[email protected]
with:
github_token: "${{ secrets.GH_PAT }}"
changelog_increment_filename: body.md
extra_requirements: "cz-conventional-gitmoji"
push: true
# debug: false
- name: Generate Release
uses: softprops/action-gh-release@v1
with:
name: humbldata v${{ env.REVISION }}
body_path: "body.md"
tag_name: v${{ env.REVISION }}
env:
GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}" |
I have a GitHub Workflow Action setup to use
commitizen-tools/commitizen-action@latest
Although, I am getting an error:
I don't know how to fix this or to commit the changes to the branch. I can check the git status before the action, but it seems that it is happening in the action. I can set
push: false
and then the error goes away, since I am no longer pushing the changes to the branch, but then the version change bump doesnt update and I would have to manually do this every time, and the changelog wouldnt be updated in my repo.The text was updated successfully, but these errors were encountered: