* Detect commit hashes from merge_group event
* Apply suggestion from @masaru-iritani
Co-authored-by: Masaru Iritani <25241373+masaru-iritani@users.noreply.github.com>
* refactor: update PullRequest type usage in getChangedFilesFromApi and related functions
* Run `npm run pack`
---------
Co-authored-by: Sascha Bratton <sascha@brattonbratton.com>
git show-ref will return all branches where end segment matches the input. This cause issues when there are both 'someBranch' and 'somePrefix/someBranch' branches. This fix ensures the correct ref is returned by explicitly matching segments after common parts (e.g. refs/heads).
* Use micromatch instead of minimatch
micromatch claims to support full Bash 4.3 spec and it actually passes all the tests.
For example this fixes processing of '!(**/*.tsx|**/*.less)' pattern - needed by #45
* Update CHANGELOG.md
* Remove usage of --no-auto-gc option
This option is not supported in git versions < 2.23.
Older git versions might be used in self-hosted runners.
* Update CHANGELOG
* Avoid code repetition with exec() and output listeners
* Improve behavior for new branches and when it's running in ACT
* Detect parent commit only if needed
* Fix parent commit detection for initial commit
* Improve logging
* Improve current ref detection
* Fix issue when base is a already fetched tag
* Fix issue when base is a already fetched tag
* Update README
* Document usage with act
* Use `git log` to get changes in latest commit
* Disable other output for `git log`
* get short name from base ref + improve loggig
* update CHANGELOG
* Rework change detection via `git diff`
Previous implementation performed simple diff between two versions. New implementation fetches on demand more commits to have the merge base between two branches. Now it will detect only changes introduced by branch that was pushed, instead of mixing with changes introduced meanwhile on the base branch.
Sascha Bratton