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
* develop:
0.4.0
Follow cosmjs upstream and improve implementation and related unittests
Add clean support for multiple transaction signatures (#11)
Added basic beam test
Fixed codec compilation
Removed not relevant test
Fixed typo
Added editor config (webstorm)
Added beam messages, fixed duplicate interface usage
Use builtin codecs
Added beam proto generation
0.3.5
Add support for ulum base denom
0.3.4
Update auto generated docs
Move types declaration dependencies in production from dev dependencies
CI/CD pipes improvement, added contributing file
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+16-16
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# Contributing
2
2
3
3
When contributing to this repository, please first discuss the change you wish to make via issue,
4
-
email, or any other method with the owners of this repository before making a change.
4
+
email, or any other method with the owners of this repository before making a change.
5
5
6
6
Please note we have a code of conduct, please follow it in all your interactions with the project.
7
7
@@ -10,7 +10,7 @@ Please note we have a code of conduct, please follow it in all your interactions
10
10
1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
11
11
2. Update the README.md with details of changes to the interface, this includes new environment variables, exposed ports, useful file locations and container parameters.
12
12
3. Increase the version numbers in any examples files and the README.md to the new version that this Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
13
-
4. You may merge the Pull Request in once you have the approval of one core team member, or if you do not have permission to do that, you may request a reviewer to merge it for you.
13
+
4. You may merge the Pull Request in once you have the approval of one core team member, or if you do not have permission to do that, you may request a reviewer to merge it for you.
14
14
15
15
## Code of Conduct
16
16
@@ -25,19 +25,19 @@ nationality, personal appearance, race, religion, or sexual identity and orienta
25
25
Examples of behavior that contributes to creating a positive environment
26
26
include:
27
27
28
-
* Using welcoming language
29
-
* Being respectful of differing viewpoints and experiences
30
-
* Gracefully accepting constructive criticism
31
-
* Focusing on what is best for the community
32
-
* Showing empathy towards other community members
28
+
- Using welcoming language
29
+
- Being respectful of differing viewpoints and experiences
30
+
- Gracefully accepting constructive criticism
31
+
- Focusing on what is best for the community
32
+
- Showing empathy towards other community members
33
33
34
34
Examples of unacceptable behavior by participants include:
35
35
36
-
* The use of sexualized language or imagery and unwelcome sexual attention or advances
37
-
* Trolling, insulting/derogatory comments, and personal or political attacks
38
-
* Public or private harassment
39
-
* Publishing others' private information, such as a physical or electronic address, without explicit permission
40
-
* Other conduct which could reasonably be considered inappropriate in a professional setting
36
+
- The use of sexualized language or imagery and unwelcome sexual attention or advances
37
+
- Trolling, insulting/derogatory comments, and personal or political attacks
38
+
- Public or private harassment
39
+
- Publishing others' private information, such as a physical or electronic address, without explicit permission
40
+
- Other conduct which could reasonably be considered inappropriate in a professional setting
41
41
42
42
### Our Responsibilities
43
43
@@ -50,14 +50,14 @@ threatening, offensive, or harmful.
50
50
51
51
### Scope
52
52
53
-
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
53
+
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
54
54
Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed
55
-
representative at an online or offline event.
55
+
representative at an online or offline event.
56
56
Representation of a project may be further defined and clarified by project maintainers.
57
57
58
58
### Enforcement
59
59
60
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at contact [ at ] lum.network.
60
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at contact [ at ] lum.network.
61
61
All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances.
62
62
The project team is obligated to maintain confidentiality with regard to the reporter of an incident.
63
63
Further details of specific enforcement policies may be posted separately.
@@ -70,4 +70,4 @@ members of the project's leadership.
70
70
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
0 commit comments