mikeal/merge-release issues and pull requests

#49 - Is this repo maintained?

Issue - State: open - Opened by kanekotic about 1 year ago - 2 comments

#48 - Added Workspace as safe.directory & fix issue with version retrieval

Pull Request - State: open - Opened by kanekotic over 1 year ago - 6 comments

#47 - fatal: not in a git directory

Issue - State: open - Opened by kanekotic over 1 year ago - 1 comment

#46 - Debian fails to get packages

Pull Request - State: closed - Opened by cosminolariu over 1 year ago - 1 comment

#45 - Version tags are not pushed

Issue - State: open - Opened by tobyjsullivan over 2 years ago - 2 comments

#42 - docs: add note about using !: to rev the major

Pull Request - State: open - Opened by achingbrain over 3 years ago - 1 comment

#41 - Invalid workflow file

Issue - State: closed - Opened by TrueXPixells over 3 years ago

#40 - More robust major release detection.

Issue - State: open - Opened by mikeal over 3 years ago

#39 - Support `!:` commit syntax for breaking changes

Pull Request - State: closed - Opened by honzabilek4 almost 4 years ago

#38 - Write to deployDir/package.json when updating version

Pull Request - State: closed - Opened by mattdsteele almost 4 years ago

#37 - Allow dry run

Issue - State: open - Opened by josejulio about 4 years ago

#36 - Didn't exit non-zero when it failed

Issue - State: open - Opened by peterbe about 4 years ago - 5 comments

#35 - feat: detect and use publish script in package.json

Pull Request - State: closed - Opened by mikeal about 4 years ago

#34 - Call "merge-release.js" directly, rather than deploying as npm package

Pull Request - State: closed - Opened by benwinding about 4 years ago - 4 comments

#33 - consider version field in package.json

Issue - State: open - Opened by Gozala about 4 years ago - 2 comments

#32 - Adds a configuration section on the README

Pull Request - State: closed - Opened by josejulio about 4 years ago

#31 - Adds option to only allow commits from a specific path to trigger the release

Pull Request - State: closed - Opened by josejulio about 4 years ago - 4 comments

#30 - Update workflow name to match the currently used

Pull Request - State: closed - Opened by josejulio about 4 years ago - 2 comments

#29 - Github tag is not released automatically

Issue - State: closed - Opened by aditya81070 over 4 years ago - 13 comments

#28 - Update the package.json file and PR?

Issue - State: closed - Opened by MrCoder over 4 years ago - 2 comments

#27 - Compatible with "version update" pushes?

Issue - State: open - Opened by elliot-nelson over 4 years ago - 7 comments

#26 - Support `!:` commit syntax for breaking changes

Issue - State: closed - Opened by mikeal over 4 years ago - 4 comments
Labels: good first issue

#25 - Update to standard formatting

Pull Request - State: closed - Opened by mattdsteele over 4 years ago

#24 - Add step output "version" parameter for other parts of the workflow

Pull Request - State: closed - Opened by benwinding over 4 years ago - 2 comments

#23 - entrypoint, avoid space clobbing

Pull Request - State: closed - Opened by glensc over 4 years ago - 1 comment

#22 - Move dependencies to a Docker Hub Image

Issue - State: open - Opened by benwinding over 4 years ago - 3 comments
Labels: help wanted

#21 - Allow custom npmrc file

Pull Request - State: closed - Opened by elliot-nelson over 4 years ago

#20 - Allow a prefix string before "feat:"

Issue - State: open - Opened by elliot-nelson over 4 years ago - 1 comment

#19 - Added functionality for mono-repos (different src and dist folders)

Pull Request - State: closed - Opened by benwinding over 4 years ago - 3 comments

#18 - Empty LICENSE File?

Issue - State: open - Opened by benwinding over 4 years ago

#17 - fix: use env var NPM_REGISTRY_URL to determine cur version

Pull Request - State: closed - Opened by beatthat over 4 years ago

#16 - One time password

Issue - State: open - Opened by bpierre over 4 years ago - 2 comments

#15 - Failing to push new tag

Issue - State: closed - Opened by gauntface over 4 years ago - 2 comments

#14 - Leave package access scope to the package configuration

Pull Request - State: closed - Opened by joscha over 4 years ago - 4 comments

#13 - Publish unpublished packages

Issue - State: open - Opened by joscha over 4 years ago - 13 comments

#12 - Script does not update package.json

Issue - State: closed - Opened by gruselhaus over 4 years ago - 2 comments

#11 - Publish to GitHub Package Registry

Issue - State: open - Opened by geoperez almost 5 years ago - 15 comments

#10 - Function for not publishing on given merges to master?

Issue - State: open - Opened by trygve-lie almost 5 years ago - 2 comments

#9 - Option to update package.json version

Issue - State: closed - Opened by EmilienLeroy almost 5 years ago - 4 comments

#8 - Support for Private/Restricted Repos and Packages

Pull Request - State: open - Opened by Jonjoe almost 5 years ago - 4 comments

#7 - Add support for publishing a package that isn't at repo root

Pull Request - State: open - Opened by adrw almost 5 years ago - 5 comments

#6 - question: Push the bumped npm version - does not work for me

Issue - State: open - Opened by ruscon almost 5 years ago - 2 comments

#5 - doc: update README to link to v2 YAML file

Pull Request - State: closed - Opened by nrn about 5 years ago - 2 comments

#4 - feat: Add tag to github repo for the commit used for the npm release

Pull Request - State: closed - Opened by fadeenk about 5 years ago - 4 comments

#3 - Error: spawn git ENOENT

Issue - State: closed - Opened by tlvince about 5 years ago - 3 comments

#2 - fix: log errors rather than allowing unhandled rejections

Pull Request - State: closed - Opened by jlipps about 5 years ago - 3 comments

#1 - Clean up commented-out code

Pull Request - State: closed - Opened by olleolleolle over 5 years ago

GitHub / mikeal/merge-release issues and pull requests