Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: hacktoberfest17/programming
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.0
Choose a base ref
...
head repository: hacktoberfest17/programming
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Choose a head ref
Loading
Showing 1,268 changed files with 71,837 additions and 58 deletions.
6 changes: 6 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
.DS_Store

.idea

# Dependencies
node_modules/
46 changes: 46 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
# Contributor Covenant 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

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at tiwari.anurag126@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

## 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/
40 changes: 22 additions & 18 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,3 @@

# HacktoberFest'17

Anyone can use this project to make their contribution to an open source project on GitHub.
@@ -11,14 +10,14 @@ This is a Public Repository open to all members of the GitHub Community. Any mem
## What is Hacktoberfest?
A month-long celebration from October 1st - 31st sponsored by [Digital Ocean](https://hacktoberfest.digitalocean.com/) and [GitHub](https://github.com/blog/2433-celebrate-open-source-this-october-with-hacktoberfest) to get people involved in [Open Source](https://github.com/open-source). Create your very first Pull Request to any Public Repository on GitHub and contribute to the Open Source Developer Community.

[https://hacktoberfest.digitalocean.com/](https://hacktoberfest.digitalocean.com/)
[https://hacktoberfest.digitalocean.com](https://hacktoberfest.digitalocean.com/)


## How Contribute to This Project
Here are 3 quick and painless ways to contribute to this project:

* Add a program in any language. (A simple Hello World would be suffice.)
To do so, first create a issue with the task you are doing. For Ex. Issue - creating bubble sort in C. Add the HacktoberFest label in the issue and assign the issue to yourself. Create a pull request in response to that issue and finally submit it for review.
To do so, first create an issue with the task you are doing. For Ex. Issue - creating bubble sort in C. Add the HacktoberFest label in the issue and assign the issue to yourself. Create a pull request in response to that issue and finally submit it for review.

* How to name your branch?
username_hello_world_in_c
@@ -32,20 +31,25 @@ Finally, wait for it to be merged!
## Getting Started
* Fork this repository (Click the Fork button in the top right of this page, click your Profile Image)
* Clone your fork down to your local machine
```markdown
git clone https://github.com/your-username/programming.git
```

```sh
$ git clone https://github.com/your-username/programming.git
```

* Create a branch
```markdown
git checkout -b branch-name
```
* Make your changes (Choose from any task below)
```sh
$ git checkout -b branch-name
```

* Make your changes
* Commit and Push
```markdown
git add .
git commit -m 'commit message'
git push origin branch-name
```

```sh
$ git add filename
$ git commit -m 'commit message'
$ git push origin branch-name
```

* Create a New Pull Request from your forked repository (Click the New Pull Request button located at the top of your repo)
* Wait for your PR review and merge approval!
* __Star this repository__ if you had fun!
@@ -58,15 +62,15 @@ Don't forget to include the comments as seen above. Feel free to include additio
Here is a great tutorial for creating your first Pull Request by [Roshan Jossey](https://github.com/Roshanjossey)
[https://github.com/Roshanjossey/first-contributions](https://github.com/Roshanjossey/first-contributions)

Managing your Forked Repo [https://help.github.com/articles/fork-a-repo/](https://help.github.com/articles/fork-a-repo/)
Managing your Forked Repo [https://help.github.com/articles/fork-a-repo](https://help.github.com/articles/fork-a-repo/)

Syncing a Fork [https://help.github.com/articles/syncing-a-fork/](https://help.github.com/articles/syncing-a-fork/)
Syncing a Fork [https://help.github.com/articles/syncing-a-fork](https://help.github.com/articles/syncing-a-fork/)

Keep Your Fork Synced [https://gist.github.com/CristinaSolana/1885435](https://gist.github.com/CristinaSolana/1885435)

Checkout this list for README examples - Awesome README [![Awesome](https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg)](https://github.com/sindresorhus/awesome)

Github-Flavored Markdown [https://guides.github.com/features/mastering-markdown/](https://guides.github.com/features/mastering-markdown/)
Github-Flavored Markdown [https://guides.github.com/features/mastering-markdown](https://guides.github.com/features/mastering-markdown/)

## Additional References Added By Contributors
GitHub license explained [https://choosealicense.com](https://choosealicense.com)
Loading