Skip to content

Commit

Permalink
Update docs slack->chat
Browse files Browse the repository at this point in the history
Change-Id: I5cc399385371bb6993a001aa444adf29fd51ed56
Signed-off-by: Ry Jones <rjones@linuxfoundation.org>
  • Loading branch information
ryjones committed Feb 7, 2017
1 parent 6c8f0be commit 9266d1e
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Before taking actions, we highly recommend reading the [docs](../README.md).
We now have two channels for bug and questions:

* [Jira](https://jira.hyperledger.org/secure/RapidBoard.jspa?rapidView=111): report bug issues, create to-do tasks.
* [Slack](https://hyperledgerproject.slack.com/archives/cello): technical discussions and questions.
* [Chat](https://chat.hyperledger.org/channel/cello): technical discussions and questions.

Jira tasks with `To Do` status are available for picking. If you want to handle one, assign it to yourself, and update the status to `In Progress`. Remember to mark it to `Done` when the patch is merged.

Expand Down Expand Up @@ -80,4 +80,4 @@ $ git review

After the review is uploaded successfully, you can open [Gerrit Dashboard](https://gerrit.hyperledger.org/r/#/dashboard/self) to invite reviewers for checking. The patch will be merged into the `master` branch if passing the reviewer checking.

* If you need to refine the patch further, you can commit the new code with `git commit -a --amend`, and then repeat the `git review` command.
* If you need to refine the patch further, you can commit the new code with `git commit -a --amend`, and then repeat the `git review` command.

0 comments on commit 9266d1e

Please sign in to comment.