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.

Sign up for GitHub

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

Jump to bottom

count #2

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

count #2

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2017bd6
count
vishal9708 Oct 9, 2018
16eacc5
contribute
vishal9708 Oct 9, 2018
be2a08b
Merge branch 'AASF-IIITM:master' into master
vishal9708 Oct 7, 2021
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
10 changes: 5 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Contributing to Repositories in Source-aasf
# Contributing to Repositories in Source-aasf
So you're interested in contributing to Source-aasf? Excellent! We appreciate your invaluable input! We want to make contributing to our projects as easy and transparent as possible, whether it's:

- Reporting a bug
Expand Down Expand Up @@ -35,11 +35,11 @@ A full git tutorial is beyond the scope of this document but this list describes

## Workflow Overview

These, conceptually, are the steps you will follow in contributing to repositories on Source-aasf:
These, conceptually , are the steps you will follow in contributing to repositories on Source-aasf:

- Fork a repository and clone it locally.
- Make a new feature branch; you will make your changes on this branch.
- Follow The editing workflow to write/edit/document/test code - make frequent, small commits.
- Follow The editing workflow to write/edit/document/test code - make frequent , small commits.
- Push changes to feature branch on your fork.
- From GitHub, ask for your changes to be reviewed to let the maintainers know you have contributions to review.
- Make a pull request from GitHub.
Expand Down Expand Up @@ -83,7 +83,7 @@ git branch my-new-feature my-project/master
git checkout my-new-feature
```

* ## Make changes to the code.
## Make changes to the code.
Then, to stage these changes run
`git add .` if you want to add all changed files or `git add <file_names>` if you want to add specific files to the staging area.
Then commit your changes with a meaningful message
Expand All @@ -96,7 +96,7 @@ On GitHub, on your forked repo, switch your branch from dropdown menu to my-new-
You will see the message of how many commits your branch is ahead of upstream/master.
Now click on Pull Request, enter a title for the set of changes, and some explanation of what you’ve done. If there is anything you’d like particular attention for, like a complicated change or some code you are not happy with, add the details here.

* ## Revise and push as necessary
## Revise and push as necessary

You may be asked to make changes in the discussion of the pull request. Make those changes in your local copy, commit them to your local repo and push them to GitHub. GitHub will automatically update your pull request.

Expand Down