Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to submit a Pull Request (PR) #8

Open
cemitch99 opened this issue Nov 12, 2024 · 1 comment
Open

How to submit a Pull Request (PR) #8

cemitch99 opened this issue Nov 12, 2024 · 1 comment

Comments

@cemitch99
Copy link
Contributor

To be done only once for each user:

  1. Go to https://github.com/campa-consortium/lattice-standard.
  2. Click the pulldown arrow next to Fork, click Create a New Fork, and specify your GitHub username in the Owner field (e.g., "cemitch99").
  3. Click Code to view and copy the url for your fork
    (e.g., https://github.com/cemitch99/lattice-standard.git)
  4. On your local machine, from the terminal, clone your fork:
    git clone https://github.com/cemitch99/lattice-standard.git

To be done each time to submit a PR, in your local repo:

  1. Change into the working directory for your local repo:
    cd lattice-standard
  2. Create a new branch with a descriptive name for the desired changes (e.g., "add_template"):
    git checkout -b add_template
  3. Make the desired changes to the local files.
    For example, add a new file "pull_request_element_template.md"
  4. View the proposed changes (optional).
    git status
  5. Add the changes to your local staging area:
    git add pull_request_element_template.md
  6. Commit the changes to your local repo, including an informative message.
    git commit -m "Add element template."
  7. Push your changes to the remote repo.
    git push origin add_template
  8. Follow the link that is generated to open a new Pull Request on GitHub that includes these changes.
    e.g., go to: https://github.com/cemitch99/lattice-standard/pull/new/add_template
  9. Add a title and additional information relevant to the Pull Request (as needed).
@DavidSagan
Copy link
Contributor

Do we want to put this in the Repo? Otherwise the instructions may get buried.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants