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 CONTRIBUTING.md #2247

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update CONTRIBUTING.md #2247

wants to merge 1 commit into from

Conversation

doutriaux1
Copy link
Contributor

@davis278 @downiec @muryanto1 this should probably further edited at some point, especially expalining the cdat repo is worthless in itself and bug fixes should be done in cdms, vcs, etc... repos.

### Pushing your changes

When you want your changes to appear publicly on your GitHub page, push
your forked feature branch's commits:

git push myuvcdat shiny-new-feature
git push -u mycdat shiny-new-feature

Here myuvcdat is the name given to your own GitHub fork, if you followed the previous instructions. You can list the remote repositories with:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'Here myuvcdat is the..' -> 'Here mycdat is the...'

origin git://github.com/UV-CDAT/uvcdat.git
myuvcdat git@github.com:yourname/uvcdat.git
origin git://github.com/CDAT/cdat.git
uvcdat git@github.com:yourname/cdat.git
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

uvcdat -> mycdat?

@downiec
Copy link

downiec commented Oct 30, 2019

Yeah documentation here should be updated, thanks Charles!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants