You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before contributing to Indy SDK, there are a couple steps that will help your process go much more smoothly.
5
+
6
+
First, please take a look at our contributing guidelines: [how to contribute to Hyperledger Indy](http://bit.ly/2ugd0bq).
7
+
8
+
If you are looking for how to sign current or previous commits, go here: [signing your commits](signing-commits.md)
9
+
10
+
## Connect with the Community
11
+
12
+
Hyperledger Indy has a vibrant and active community of developers willing to help you answer questions, learn more about self-sovereign identity, and get involved.
13
+
14
+
You will find the best and most update resources on chat board here: [Hyperledger Rocket Chat](https://chat.hyperledger.org/home)
15
+
16
+
\#indy-sdk, \#indy-node, and \#indy are the some of the best channels to get started. Please introduce yourself and let us know what you want to accomplish!
17
+
18
+
## How to Start Working with the Code
19
+
20
+
1. Fork the indy-sdk repository on Github to your personal account.
21
+
22
+
1. Add the hyperledger/indy-sdk as the remote upstream:
If you setup the demo and encounter a 307 error recommend to take the following steps to cleanup and start over. The communication with the ledger is affected and it is not possible to run the demo. Here are some recommendations for other errors.
4
+
* 306: you already have a configured ledger. Perform clean start.
5
+
* 301: you are trying to create a ledger but it is already configured. A single failure will cause a problem when opening the ledger. Perform clean install.
6
+
* 212: wallet is not found. When this occur stop and start container: Ctrl-C, docker-compose down, docker-compose up
7
+
8
+
## Overview steps for clean start
9
+
10
+
1. Remove existing instances
11
+
1. Reset source files
12
+
1. Perform a new build
13
+
1. Start demo
14
+
15
+
## Steps in detail
16
+
17
+
1. Make sure containers are closed
18
+
19
+
```
20
+
docker-compose down # to make sure containers are closed
21
+
docker image ls # find image names that need to be removed in next step
22
+
docker image rm getting-started
23
+
docker image rm indy_pool
24
+
docker volume ls # find volume name that needs to be removed in next step
25
+
docker volume rm gettingstarted_sandbox
26
+
```
27
+
28
+
2. Reset source files
29
+
30
+
```git tag # choose the latest version and use it as <branch_name>
31
+
git checkout <branch_name>
32
+
git reset --hard **WARNING** : make copies of any changes you want to keep prior to taking this step
33
+
git fetch --all
34
+
git pull
35
+
```
36
+
37
+
3. Perform a new build
38
+
39
+
```
40
+
docker-compose build --no-cache # adding no cache to make clean build
If you are here because you forgot to sign your commits, fear not. Check out [how to sign previous commits](#how-to-sign-previous-commits)
4
+
5
+
We use developer certificate of origin (DCO) in all hyperledger repositories, so to get your pull requests accepted, you must certify your commits by signing off on each commit.
6
+
7
+
## Signing your current commit
8
+
-`$ git commit -s -m "your commit message"`
9
+
- To see if your commits have been signed off, run `$ git log --show-signature`
10
+
- If you need to re-sign the most current commit, use `$ git commit --amend --no-edit -s`.
11
+
12
+
The `-s` flag signs the commit message with your name and email.
13
+
14
+
## How to Sign Previous Commits
15
+
1. Use `git log --show-signature` to see which commits need to be signed.
16
+
1. Go into interactive rebase mode using `$ git rebase -i HEAD~X` where X is the number of commits up to the most current commit you would like to see.
17
+
1. You will see a list of the commits in a text file. **On the line after each commit you need to sign**, add `exec git commit --amend --no-edit -s` with the lowercase `-s` adding a text signature in the commit body. Example that signs both commits:
18
+
```
19
+
pick 12345 commit message
20
+
exec git commit --amend --no-edit -s
21
+
pick 67890 commit message
22
+
exec git commit --amend --no-edit -s
23
+
```
24
+
1. If you need to re-sign a bunch of previous commits at once, find the earliest unsigned commit using `git log --show-signature` and use that the HASH of the commit before it in this command: `git rebase --exec 'git commit --amend --no-edit -n -s' -i HASH`. This will sign every commit from most recent to right before the HASH.
25
+
1. You will probably need to do a force push `git push -f` if you had previously pushed unsigned commits to remote.
0 commit comments