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

Update readme.md #1

Merged
merged 1 commit into from
Mar 29, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
74 changes: 74 additions & 0 deletions learning/dashboard/PR_ISSUE/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,3 +81,77 @@ Write a clear and descriptive title and description for the pull request, includ

#### Step14:
Submit the pull request.

## Submit the PR with commits from all contributors assigned to the PR.

To submit a pull request (PR) with commits from all contributors assigned to the PR, follow these steps:

#### Step1:
Clone the repository to your local machine:

`git clone <repository_url>`

#### Step2:
Create a new branch for your changes:

`git checkout -b <branch_name>`

#### Step3:
Make the necessary changes and commit them:

`git add .
git commit -m "commit message"`

#### Step4:
Push the changes to the remote repository:

`git push origin <branch_name>`

#### Step5:
Once you have pushed your changes, go to the repository on GitHub and click on *"New pull request"*.

#### Step6:
Choose the branch you just pushed your changes to as the *"head"* branch and select the target branch you want to merge your changes into.

#### Step7:
Add a description to your pull request, explaining what changes you made and why.

#### Step8:
If other contributors have made changes to the same files you modified, their commits will be included in the pull request automatically. If there are no other contributors, skip to step 9.

#### Step9:
If other contributors have made changes to the same files you modified, you will need to merge their changes into your branch before submitting the pull request. To do this, run the following command:

`git fetch origin`
`git merge origin/<target_branch>`

#### Step10:
Resolve any merge conflicts that arise.

#### Step11:
Once you have resolved any conflicts and all contributors' changes are included in your branch, push your changes to the remote repository:

`git push origin <branch_name>`

#### Step12:
Go back to your pull request on GitHub and click on *"Create pull request"*.

Review your changes and click on *"Create pull request"* again to submit your PR with commits from all contributors assigned to the PR.



## Use this for all the contributions where more than one contributor is assigned.

When multiple contributors are assigned to a project or task, using a PR (pull request) can help streamline the collaboration process and ensure that everyone is on the same page. Here are some steps to follow when using a PR for collaborative contributions:
#### Step1:
Create a branch for the new feature or changes you want to make. This will help keep your changes separate from the main codebase until they are ready to be merged in.
#### Step2:
Make the necessary changes and commit them to your branch. Ensure that your changes are consistent with the project's goals and that you have tested them thoroughly.
#### Step3:
Create a PR and assign it to the relevant contributors. This will notify them of the changes you have made and allow them to review and provide feedback on your changes.
#### Step4:
Respond to feedback and make any necessary changes. This is an iterative process, so expect to go back and forth a few times until everyone is happy with the changes.
#### Step5:
Once the changes have been approved, merge the changes into the main codebase. Be sure to resolve any merge conflicts that may arise and update the relevant documentation as necessary.
#### Step6:
Celebrate your success and reflect on the collaboration process. Identify what worked well and what could be improved for future PRs.