Skip to content

Releases: changesets/ghcommit

v2.0.0

10 May 09:37
3d63783
Compare
Choose a tag to compare

Major Changes

  • #41 295d847 Thanks @s0! - Make repo argument required,
    and remove the repository argument which was deprecated
    and previously could be used in its place.

  • #40 4117e39 Thanks @s0! - Refactor & clean up options for multiple functions

    • For commitFilesFromDirectory:
      • Rename workingDirectory to cwd for consistency across repos,
        and utils like exec
      • Make cwd a required argument
    • For commitChangesFromRepo:
      • Merge repoDirectory and addFromDirectory into a single required argument
        cwd. This folder will now both be used to filter which files are added,
        and to find the root of the repository.
      • Introduce recursivelyFindRoot option (default: true),
        to optionally search for the root of the repository,
        by checking for existence of .git directory in parent directories,
        starting from cwd.

    This effectively removes all usage of process.cwd() within the package,
    instead requiring all usage to be very explicit with specifying paths.

v1.4.0

08 May 09:28
b3e603b
Compare
Choose a tag to compare

Minor Changes

  • #37 21c9eaf Thanks @s0! - Throw an error when executable files are encountered

  • #33 92be707 Thanks @s0! - Introduce filterFiles argument for commitChangesFromRepo

    Allow for a custom function to be specified to filter which files should be
    included in the commit

  • #33 92be707 Thanks @s0! - Introduce addFromDirectory option for commitChangesFromRepo to allow users to
    specify 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 in commitChangesFromRepo
    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 not
    work when run from a subdirectory of a repo when repoDirectory was not
    specified.

Patch Changes

  • #34 231d400 Thanks @h3rmanj! - More gracefully handle symlinks, and ignore them when included in .gitignore

v1.3.1

06 May 20:08
99331af
Compare
Choose a tag to compare

Patch Changes

v1.3.0

02 May 10:48
47e9fa1
Compare
Choose a tag to compare

Minor Changes

@s0/ghcommit

v1.2.1

02 Nov 11:04
80aa73e
Compare
Choose a tag to compare

Patch Changes

  • 85ec677: Address issue with Ref HEAD not found

v1.2.0

25 Aug 17:13
d02e881
Compare
Choose a tag to compare

Minor Changes

  • a704fb3: Rename repository argument to repo, and deprecate old argument
  • a704fb3: Allow message to be specified as single string

v1.1.0

25 Aug 13:13
1506f8c
Compare
Choose a tag to compare

Minor Changes

  • 642fb77: Allow for base commit to be specified with commitChangesFromRepo

v1.0.0

23 Aug 22:06
b127b6e
Compare
Choose a tag to compare

Major Changes

v0.1.0

14 Jul 15:35
fce2760
Compare
Choose a tag to compare

Minor Changes