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
Thank you for considering making contributions to `algebra`!
4
+
5
+
Contributing to this repository can be done in several forms, such as participating in discussion or proposing code changes.
6
+
To ensure a smooth workflow for all contributors, the following general procedure for contributing has been established:
7
+
8
+
1) Either open or find an issue you'd like to help with
9
+
2) Participate in thoughtful discussion on that issue
10
+
3) If you would like to contribute:
11
+
* If the issue is a feature proposal, ensure that the proposal has been accepted
12
+
* Ensure that nobody else has already begun working on this issue.
13
+
If they have, please try to contact them to collaborate
14
+
* If nobody has been assigned for the issue and you would like to work on it, make a comment on the issue to inform the community of your intentions to begin work. (So we can avoid duplication of efforts)
15
+
* We suggest using standard GitHub best practices for contributing: fork the repository, branch from the HEAD of `master`, make some commits on your branch, and submit a PR from the branch to `master`.
16
+
More detail on this is below
17
+
* Be sure to include a relevant changelog entry in the Pending section of CHANGELOG.md (see file for log format)
18
+
* If the change is breaking, we may add migration instructions.
19
+
20
+
Note that for very small or clear problems (such as typos), or well isolated improvements, it is not required to an open issue to submit a PR.
21
+
But be aware that for more complex problems/features touching multiple parts of the codebase, if a PR is opened before an adequate design discussion has taken place in a GitHub issue, that PR runs a larger likelihood of being rejected.
22
+
23
+
Looking for a good place to start contributing? How about checking out some good first issues
24
+
25
+
## Branch Structure
26
+
27
+
`algebra` has its default branch as `master`, which is where PRs are merged into. Releases will be periodically made, on no set schedule.
28
+
All other branches should be assumed to be miscellaneous feature development branches.
29
+
30
+
All downstream users of the library should be using tagged versions of the library pulled from cargo.
31
+
32
+
## How to work on a fork
33
+
34
+
Please skip this section if you're familiar with contributing to opensource GitHub projects.
35
+
36
+
First fork the repository from the GitHub UI, and clone it locally.
37
+
Then in the repository, you want to add the repository you forked from as a new remote. You do this as:
0 commit comments