...
- git clone https://github.com/apache/incubator-nuttx nuttx
- git clone https://github.com/apache/incubator-nuttx-apps apps
These will create copies, clones, of the Apache NuttX repositories on your local computer.
Enter inside "nuttx" directory and, if you like, create a branch where you will work:
- cd nuttx
- git checkout -b mybranch origin/dev
Make your modification and commit them as described later in this document.
Clones of repositories are useful for creating patches that you can send to the Apache project for inclusion. A better workflow, however, would use pull requests and to use pull requests you will need to use a fork instead of a clone.
Make your modification and commit it.
Forking the Repositories: A fork of the repository is a clone of the origin repository that exists in your remote GitHub user area. The "fork & pull" model lets anyone fork an existing repository and push changes to their personal fork without requiring access be granted to the source repository. The changes must then be pulled into the source repository by the project maintainer. This model reduces the amount of friction for new contributors and is popular with open source projects because it allows people to work independently without upfront coordination.
The forked repository is mostly static. It exists in order to allow you to publish work for code review purposes. You don't do active development in your forked repository (in fact, you can't; because it doesn't exist repository as would do with a cloned repository. Unlike the cloned respository, the fork does not exist on your computer, it exists on GitHub's server in the cloud). Instead, you would do your development on a clone of the fork of the repository.
To create a fork of your repository, follow these steps (from https://help.github.com/en/github/getting-started-with-github/fork-a-repo):
...