Let's work with forks and branches
@isandom is already working on this.
Since Jul 6, 2022.
- Dominant language
- Jupyter Notebook
- Stars
- 4
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Let's start working with forks, branches, and pull requests. This is what we will do from now on:
1- Make your own fork of this repository. Do not push changes straight to the uibcdf/OpenENM if not necessary. Do not work with this repo, work with your fork.
2- Clone your forked repository in your machine.
3- Any change, modification, implementation... do it in a new branch (different from main) in your fork.
4- Create and work with as many branches as you need. Once the implementation developed in your branch XXX has been finished, make a PR (Pull Request) from XXX (of your fork) to the branch main of the uibcdf repository.
5- PRs will be reviewed always by one of the main developers different from the author (at this point I review your PRs, and you mine).
6- Once a PR has been reviewed, accepted, and merged, you have to fetch the new changes from the main branch of uibcdf repo to your main branch (fork repo). Keep always your main branch of your fork updated with the main branch of this repository.
I am sure that you will have many doubts about this process. This is the place to ask. Courage! 💪🏻
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.