From 8085e86170d281403520efd643ef63ea36bfa98c Mon Sep 17 00:00:00 2001 From: Karen Shea Date: Fri, 20 Apr 2018 13:19:48 +0200 Subject: [PATCH] Change emoji --- docs/releasing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/releasing.md b/docs/releasing.md index 1fe032f67..9a492cd49 100644 --- a/docs/releasing.md +++ b/docs/releasing.md @@ -44,7 +44,7 @@ We may introduce forward-compatible changes: query parameters and response prope 1. Check out the appropriate release branch `x.y` 2. Make sure `CHANGELOG.md` is up to date. 3. Make sure the `package.json` on branch `x.y` has been committed. -4. Make sure all tests are passing (e.g. Travis CI gives you a :thumbs_up:) +4. Make sure all tests are passing (e.g. Travis CI gives you a :green_apple:) 5. Use an annotated tag to mark the release: `git tag vx.y.z -a` Body of the tag description should be the changelog entries. Commit should be one in which the `package.json` version matches the version you want to release. 6. Use `npm run docs` to generate the API documentation. Copy `build/docs/*` to `https://github.com/Project-OSRM/project-osrm.github.com` in the `docs/vN.N.N/api` directory 7. Push tags and commits: `git push; git push --tags`