rlespinasse / git-commit-data-action Goto Github PK

To follow best practices on semver

In addition to the environment variables, we want to access the values as action outputs.

- id: git-commit-data
  name: Expose git commit data
  uses: rlespinasse/git-commit-data-action@v1
- run: |
     echo "${{ steps.git-commit-data.outputs.sha }} is the same as ${{ env.GIT_COMMIT_SHA }}"
     echo "${{ steps.git-commit-data.outputs.author }} is the same as ${{ env.GIT_COMMIT_AUTHOR }}"

The publish-env input (as boolean) enables us to disable the publication as an environment variable.

If we follow https://github.com/actions/toolkit/blob/master/docs/action-versioning.md#versioning, this action needs to have a v1 tag that follows the latest release on the v1.x branch

See rlespinasse/release-that#17

I'm getting the following error after updating to the latest version (1.1.1)

Run rlespinasse/[email protected]
Started: bash /home/runner/work/_actions/rlespinasse/git-commit-data-action/1.1.1/entrypoint.sh
Error: Unable to process file command 'env' successfully.
Error: Invalid environment variable value. Matching delimiter not found 'EOF'

This is the action

      - name: Expose git commit data
        uses: rlespinasse/[email protected]

Here's the failing run:
https://github.com/yoavain/easylists-for-pihole/runs/2153199930?check_suite_focus=true

Since all the real work is done in a script, we can remove the javascript wrapper around that script and use it directly in a composite-based action without breaking changes.

see https://github.com/rhysd/actionlint

In order to improve the governance and the future of this action, I created a GitHub organization called Actions-Able which is composed of other action maintainers and co-maintainers I work with.

This issue concerns preparing the migration to this new ownership without breaking the current use of rlespinasse/git-commit-data-action@... in our user workflows.