Update docs section about using the Action in public forks.
Add warning about current issue when the forks lives under an organisation.
Mark section about running a workflow in the head repository as outdated, as I was not able to reproduce this in test projects.
See https://github.com/stefanzweifel/git-auto-commit-action/issues/211#issuecomment-1428849944 for more details.
Starting February 2nd 2023, GitHub changed the default permissions of the GITHUB_TOKEN to be read-only in all new repositories.[1]
git-auto-commits needs `write`-permissions for the `contents`-key in order to work properly.
This commits updates the usage section, to mention the need for the permission requirements. The examples have also been updated to reflect that change.
[1]: https://github.blog/changelog/2023-02-02-github-actions-updating-the-default-github_token-permissions-to-read-only/
* Add _set_github_output function
* Use _set_github_output in Action
* Add _log function
* Use _log in Action and fix Test Cases
* Update wording in log messages
* Update note about removal of old output syntax
Logic is now encapuslated in a single function. I don’t mind keeping it around until spring / June 2023
* fix crlf test
* add diff check before commit
* add dirty check flag (not sure if needed)
* Update test name and add more assertions
Update test name to make it clear that the Action no longer fails to detect CRLF changes.
* Add Comment to explain why we use git-diff again
* Add test to confirm content changes are commited
* Closes#241
Co-authored-by: Stefan Zweifel <hello@stefanzweifel.io>
* GitHub has deprecated set-output and now needs to add the content to the GITHUB_OUTPUT file
* Update tests too
* Fix tests and shell-format changes
* Revert yarn.lock changes
This PR adds a test to confirm, that changes to CRLF are not properly detected and that the message "Working tree clean. Nothing to commit." is displayed.
Setting `core.autocrlf` to `true` also has no effect here.
refs #241
* Expand file_pattern input
* Expand file pattern array in git-status
* Add Failing Test
* Expand INPUT_FILE_PATTERN
* Fix Shellcheck Issues
* Add test to cover file expansion works when globbing is disabled
* Add explanation to README
This test confirms the problem mentioned in #227.
If `file_pattern` contains a pattern of, for example 2 file extensions, and only files for one extensions are dirty but not for the otherone, `git-add` will throw a fatal error.
It does not throw an error if the files for the pattern already exist but are not dirty.
