From dde04759cf7c93ca17ec1a65804221b48ea6c290 Mon Sep 17 00:00:00 2001 From: cyian-1756 Date: Fri, 15 Jun 2018 22:58:39 -0400 Subject: [PATCH] Wrote a page detailing how to publish a new ripme release --- How-to-make-a-new-ripme-release.md | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 How-to-make-a-new-ripme-release.md diff --git a/How-to-make-a-new-ripme-release.md b/How-to-make-a-new-ripme-release.md new file mode 100644 index 0000000..eab34c9 --- /dev/null +++ b/How-to-make-a-new-ripme-release.md @@ -0,0 +1,11 @@ +Note: To make a new ripme release you must have write access to ripmeapp/ripme and have a github api token + +Step 1: Update your local copy of ripme with `git pull origin master` + +Step 2: Run patch.py. This script will prompt you for a list of changes (separated with a ;) since the last release and then update ripmes version number in a few places and append the list of changes you entered to the change log in ripme.json and commits these changes + +Step 3: Run `git push origin master` to update the remote copy of ripme + +Step 4: Run release.py. This script has several flags 2 of which are needed to push a new release, these being --file (the path to the jar built by patch.py in step 2, this is normally in target/.) and --token (Your github api token). This will make and publish the new release + +Warning: The jar you are releasing must be in target/ or release.py will crash \ No newline at end of file