Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@changesets/ghcommit@1.4.0
Minor Changes
#37
21c9eaf
Thanks @s0! - Throw an error when executable files are encountered#33
92be707
Thanks @s0! - IntroducefilterFiles
argument forcommitChangesFromRepo
Allow for a custom function to be specified to filter which files should be
included in the commit
#33
92be707
Thanks @s0! - IntroduceaddFromDirectory
option forcommitChangesFromRepo
to allow users tospecify a subdirectory of the git repository that should be used to add files
from, rather then adding all changed files.
This is useful when trying to emulate the behavior of running
git add .
from a subdirectory of the repository.
#33
92be707
Thanks @s0! - Automatically find root incommitChangesFromRepo
when
repoDirectory
is unspecified.While this does result in a behavioral change for an existing argument,
it's considered non-breaking as before
commitChangesFromRepo
would just notwork when run from a subdirectory of a repo when
repoDirectory
was notspecified.
Patch Changes
231d400
Thanks @h3rmanj! - More gracefully handle symlinks, and ignore them when included in .gitignore