René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[feature] cz action to output commit sha","articleBody":"# Feature:\n\nCommitizen gh action outputs the sha of the commit as an output to be used for downstream builds\n\n```yaml\n   steps:\n      - uses: actions/checkout@v4\n        with:\n          ref: ${steps.cz.outputs.sha}\n```\n\n# Background\n\n\n\nWe want to display the current build to the user in the UI of an api we are making with fastapi. To do this, we use the version in the `pyproject.toml`. However, Github actions does not checkout the latest commit on checkout, only the commit that triggered the gh workflow. Thus, when we add the version information before building the container, the latest commit from commitizen action is not added to the checked out code that builds the container. To solve this, we can add the following to our workflow:\n\n```yaml\n    steps:\n      - uses: actions/checkout@v4\n        with:\n          fetch-depth: 0\n          ref: main\n```\naccording to this issue in gh checkout action https://github.com/actions/checkout/issues/439. However, this this is sub-optimal for larger codebase where someone could merge to main between the commitizen bump and the gh action checkout operation. This would result in subsequent build of the wrong codebase. Suggested solution is to output the sha in the commitizen action when a commit is made so the sha can be used for subsequent checkouts.\n\n```yaml\n   steps:\n      - uses: actions/checkout@v4\n        with:\n          ref: ${steps.cz.outputs.sha}\n```\n\n\n\n","author":{"url":"https://github.com/reinthal","@type":"Person","name":"reinthal"},"datePublished":"2025-01-27T12:34:59.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/98/commitizen-action/issues/98"}