-
Notifications
You must be signed in to change notification settings - Fork 481
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1 from Gayathry17/master
updates
- Loading branch information
Showing
5 changed files
with
149 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
|
||
# Please note we have a code of conduct, please follow it in all your interactions with the project. | ||
|
||
|
||
## Code of Conduct | ||
|
||
### Our Pledge | ||
|
||
In the interest of fostering an open and welcoming environment, we as | ||
contributors and maintainers pledge to making participation in our project and | ||
our community a harassment-free experience for everyone, regardless of age, body | ||
size, disability, ethnicity, gender identity and expression, level of experience, | ||
nationality, personal appearance, race, religion, or sexual identity and | ||
orientation. | ||
|
||
### Our Standards | ||
|
||
Examples of behavior that contributes to creating a positive environment | ||
include: | ||
|
||
* Using welcoming and inclusive language | ||
* Being respectful of differing viewpoints and experiences | ||
* Gracefully accepting constructive criticism | ||
* Focusing on what is best for the community | ||
* Showing empathy towards other community members | ||
|
||
Examples of unacceptable behavior by participants include: | ||
|
||
* The use of sexualized language or imagery and unwelcome sexual attention or | ||
advances | ||
* Trolling, insulting/derogatory comments, and personal or political attacks | ||
* Public or private harassment | ||
* Publishing others' private information, such as a physical or electronic | ||
address, without explicit permission | ||
* Other conduct which could reasonably be considered inappropriate in a | ||
professional setting | ||
|
||
|
||
### Attribution | ||
|
||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, | ||
available at [http://contributor-covenant.org/version/1/4][version] | ||
|
||
[homepage]: http://contributor-covenant.org | ||
[version]: http://contributor-covenant.org/version/1/4/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,73 @@ | ||
## Contributing Guidelines | ||
|
||
Thank you for your interest in contributing. Here's everything you'll need to make your first contribution. | ||
|
||
### What can I help with? | ||
|
||
We welcome contributions of all sorts. Even the most minor changes are warmly welcomed. You may choose to work on an existing issue or propose your own. | ||
|
||
Some examples of contributions are: | ||
|
||
1. Documentation: From spell corrections to documenting the necessary information, all comes in this section. | ||
|
||
2. Bugs: Any bug fixes are counted in this section. If you see a new bug, feel free to create a new issue mentioning the problem faced. | ||
|
||
3. Feature Requests: If you would like to see some new features around the website, you can always create a new issue mentioning the requested feature. | ||
|
||
**Important:** Every PR must correspond to an issue. If there isn't an issue related to the PR, open a new issue in the Issues section. | ||
|
||
### Grabbing an issue | ||
|
||
To work on an existing issue, comment on it and say you're working on that issue. Any maintainer will assign you to the issue. This is to avoid conflicts with others also working on the issue. | ||
|
||
You can always seek help and are recommended to discuss the course of action and design decisions to tackle the issue on the issue page before making the Pull Request. | ||
|
||
### How to Contribute? | ||
|
||
1. Fork this repository. | ||
|
||
2. Check out to a new branch for the patch. | ||
|
||
```bash | ||
git checkout -b <branch name> | ||
``` | ||
|
||
3. Write your code. | ||
|
||
<!-- add any more guidelines for formatting and linting if required --> | ||
|
||
4. Before committing changes, you should verify if the issue is fixed | ||
|
||
5. Commit your changes. Try to follow the [best practices](https://gist.github.com/robertpainsi/b632364184e70900af4ab688decf6f53) while committing changes. | ||
|
||
```bash | ||
git commit -s | ||
# Then write the commit message and save changes | ||
``` | ||
|
||
6. Push the changes to your fork. | ||
|
||
```bash | ||
git push -u origin <branch name> | ||
``` | ||
|
||
7. Create a pull request. Be sure to read and follow our pull request guidelines! | ||
|
||
8. Wait for code review and address any issues raised. | ||
|
||
9. Voila! You made a contribution. Keep it up. | ||
|
||
### Keeping your fork up-to-date | ||
|
||
1. Add this repository as an upstream. | ||
<!-- add name of your upstream repo --> | ||
```bash | ||
git remote add upstream https://github.com/hhhrrrttt222111/developer-portfolio.git | ||
``` | ||
|
||
2. Pull the latest changes from the main branch. | ||
|
||
```bash | ||
git pull upstream master | ||
``` | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters