Skip to content

Add working-directory argument #8

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

Closed
evetion opened this issue Mar 24, 2021 · 6 comments · Fixed by #90
Closed

Add working-directory argument #8

evetion opened this issue Mar 24, 2021 · 6 comments · Fixed by #90

Comments

@evetion
Copy link

evetion commented Mar 24, 2021

So we can run this action in a different subdirectory in case of larger/mono repositories:

      - name: Create bump and changelog
        uses: commitizen-tools/commitizen-action@master
        with:
          github_token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
          working-directory: backend  <--
@woile
Copy link
Member

woile commented Mar 24, 2021

Interesting. How would this work? Would you have to re-use the same action for multiple directories?

@evetion
Copy link
Author

evetion commented Mar 31, 2021

Interesting question, I guess you would. My current changes: diff-fork just change the working directory so it can find the pyproject.toml stored in our backend folder. Let me know if you'd like that as a PR.

@woile
Copy link
Member

woile commented Dec 16, 2021

I missed this, feel free to open a PR. Is it working for you this way?

Could you add some documentation over this workflow? Thanks!

@Kurt-von-Laven
Copy link
Contributor

See https://github.bestrui.topmunity/t/best-practices-for-adding-reusable-workflows-to-actions/246224 for another use case for this feature (essentially arguing the case for working-directory being globally supported, but for now it would be handy to have in Commitizen).

@woile
Copy link
Member

woile commented Mar 3, 2023

Is this feature still desired?

@pietzschke
Copy link

Yeah, would be great to have it on board!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants