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
{{ message }}
This repository was archived by the owner on Jan 12, 2024. It is now read-only.
If you navigate to the following address `http://localhost:3000/ipfs/bafybeicqzoixu6ivztffjy4bktwxy6lxaxkvnavkya7kfgwyhx4bund2ga/` it should load a
79
-
page from ipfs and appear as:
148
+
## Contributing
80
149
81
-

150
+
Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are **greatly appreciated**.
82
151
83
-
### Run tests
152
+
1. Fork the IPFS Project
153
+
2. Create your Feature Branch (`git checkout -b feature/amazing-feature`)
154
+
3. Commit your Changes (`git commit -a -m 'feat: add some amazing feature'`)
155
+
4. Push to the Branch (`git push origin feature/amazing-feature`)
The IPFS implementation in JavaScript needs your help! There are a few things you can do right now to help out:
163
+
164
+
Read the [Code of Conduct](https://github.com/ipfs/community/blob/master/code-of-conduct.md) and [JavaScript Contributing Guidelines](https://github.com/ipfs/community/blob/master/CONTRIBUTING_JS.md).
165
+
166
+
-**Check out existing issues** The [issue list](https://github.com/ipfs/js-ipfs/issues) has many that are marked as ['help wanted'](https://github.com/ipfs/js-ipfs/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22help+wanted%22) or ['difficulty:easy'](https://github.com/ipfs/js-ipfs/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Adifficulty%3Aeasy) which make great starting points for development, many of which can be tackled with no prior IPFS knowledge
167
+
-**Look at the [IPFS Roadmap](https://github.com/ipfs/roadmap)** This are the high priority items being worked on right now
168
+
-**Perform code reviews** More eyes will help
169
+
a. speed the project along
170
+
b. ensure quality, and
171
+
c. reduce possible future bugs.
172
+
-**Add tests**. There can never be enough tests.
173
+
-**Join the [Weekly Core Implementations Call](https://github.com/ipfs/team-mgmt/issues/992)** it's where everyone discusses what's going on with IPFS and what's next
0 commit comments