Skip to content

Commit

Permalink
feat: read events from please.json (can still be overridden by params)
Browse files Browse the repository at this point in the history
  • Loading branch information
adhocore committed Sep 27, 2019
1 parent 7febd62 commit cfecd24
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 3 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,11 +18,11 @@ Actually you can release any thing not just PHP/Nodejs. Please itself is [releas
- Bump the version as per semver, reflect that into `./VERSION` file and commit it
- If any of the latest commits start with `feat` `<minor>` is bumped
- But if only you didnt explicitly pass `scope` already
- Release the new version and tag to github
- If there is `package.json` file, bump `package.json#version` and commit it
- If `package.json#private` is not set to `true`
- If npm user not already logged in, run `npm adduser`
- Run `npm publish` finally
- Release the new version and tag to github
- If there is `box.json` file, compile phar using `box`
(download `box.phar` if required)
- Upload the compiled `phar` as asset for the recent release
Expand Down
5 changes: 3 additions & 2 deletions please
Original file line number Diff line number Diff line change
Expand Up @@ -236,7 +236,9 @@ trigger() # $1 = event
GCFMT="%s (%an)" # git commit log format
REPO=`git config --get remote.origin.url | sed -e 's/git@github.com://;s/https:\/\/github.com\///;s/.git//'`
if [ -f ./please.json ]; then
eval $(cat ./please.json | jq -r 'to_entries|map("EVENTS[\(.key)]=\"\(.value)\"")|.[]')
fi
# argv parsing
while [[ $# -gt 0 ]]
Expand Down Expand Up @@ -385,7 +387,6 @@ if [[ $GPUSH -eq 1 ]]; then
ok
fi
# github release
trigger before-github
info "Releasing $NEXT_VERSION ..."
Expand Down

0 comments on commit cfecd24

Please sign in to comment.