Create an issue on original repo with a specific action or goal (see here for details)
Create a new branch on forked repo based on the latest pull on development branch; name the branch after the issue (e.g., using the issue number, issue68, or topically, add-contrib)
Push the branch to the remote in forked repo
Create a pull request (see here for details) using the development branch as the base and your new branch as the head
Link the pull request to the issue using the Development option (see here for details); only works for users with write capabilities on the repo.
Use GitHub pull request review and discussion space to vet changes before they are merged into the development branch
Once development branch reaches a certain milestone, merge into master as a new release
This is a test of the following workflow: