Skip to content

Add working-directory argument #8

Closed
@evetion

Description

@evetion

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  <--

Activity

woile

woile commented on Mar 24, 2021

@woile
Member

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

evetion

evetion commented on Mar 31, 2021

@evetion
Author

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

woile commented on Dec 16, 2021

@woile
Member

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

Kurt-von-Laven commented on Apr 21, 2022

@Kurt-von-Laven
Contributor

See https://github.community/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

woile commented on Mar 3, 2023

@woile
Member

Is this feature still desired?

pietzschke

pietzschke commented on Nov 14, 2023

@pietzschke

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Add `working-directory` argument · Issue #8 · commitizen-tools/commitizen-action