-
-
Notifications
You must be signed in to change notification settings - Fork 88
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 CONTRIBUTING.md #516
Conversation
Added content for the Your First Code Contribution Section
@eliezerjoel is attempting to deploy a commit to the lucavallin Team on Vercel. A member of the Team first needs to authorize it. |
Go to the original repository on GitHub. | ||
Click the "Compare & pull request" button that appears for your branch. | ||
Fill in the details for your pull request: | ||
Write a clear title and description of the changes you’ve made. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Write a clear title and description of the changes you’ve made. | |
- Write a clear title and description of the changes you’ve made. |
Click the "Compare & pull request" button that appears for your branch. | ||
Fill in the details for your pull request: | ||
Write a clear title and description of the changes you’ve made. | ||
Reference the issue your pull request fixes, if applicable (e.g., "Fixes #123"). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reference the issue your pull request fixes, if applicable (e.g., "Fixes #123"). | |
- Reference the issue your pull request fixes, if applicable (e.g., "Fixes #123"). |
#### 9. Collaborate and Improve | ||
A maintainer will review your pull request. They might ask for changes, so be ready to discuss and make updates if needed. | ||
Once your pull request is approved, it will be merged into the main branch! | ||
#### 10. Celebrate! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#### 10. Celebrate! | |
#### 10. Celebrate! |
Fill in the details for your pull request: | ||
Write a clear title and description of the changes you’ve made. | ||
Reference the issue your pull request fixes, if applicable (e.g., "Fixes #123"). | ||
#### 9. Collaborate and Improve |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#### 9. Collaborate and Improve | |
#### 9. Collaborate and Improve |
Once you're happy with your changes, push your branch to your forked repository: | ||
|
||
`git push origin your-branch-name` | ||
#### 8. Open a Pull Request |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#### 8. Open a Pull Request | |
#### 8. Open a Pull Request |
#### 3. Set Up Your Local Environment | ||
Follow the setup instructions provided in the README.md file to install any necessary dependencies and run the project locally. | ||
Make sure everything is working as expected before making any changes. | ||
#### 4. Create a Branch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#### 4. Create a Branch | |
#### 4. Create a Branch |
Check the issues page of the repository. | ||
Look for issues labeled "good first issue" or "help wanted". These issues are typically more beginner-friendly and suitable for new contributors. | ||
If you find an issue you're interested in, comment on the issue to let the maintainers know you're planning to work on it. | ||
#### 2. Fork the Repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#### 2. Fork the Repository | |
#### 2. Fork the Repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, left a few suggestions!
Added content for the Your First Code Contribution Section
Closes #515.