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

Rename Stoppable to Pausable #6

Closed
maraoz opened this issue Aug 19, 2016 · 6 comments
Closed

Rename Stoppable to Pausable #6

maraoz opened this issue Aug 19, 2016 · 6 comments
Labels
good first issue Low hanging fruit for new contributors to get involved!

Comments

@maraoz
Copy link
Contributor

maraoz commented Aug 19, 2016

See Pause in http://vessenes.com/we-need-some-best-practices-for-smart-contracts/

maraoz pushed a commit that referenced this issue Nov 24, 2016
@maraoz maraoz added the feature New contracts, functions, or helpers. label Dec 19, 2016
@maraoz maraoz changed the title Pausable contracts Rename Stoppable to Pausable Dec 19, 2016
@maraoz maraoz added chore good first issue Low hanging fruit for new contributors to get involved! and removed feature New contracts, functions, or helpers. labels Dec 19, 2016
@JGcarv
Copy link
Contributor

JGcarv commented Jan 31, 2017

Hi! I'm interested in tackling this issue, since I'm still scared of open source contributions, and this one seems pretty manageable. So, just to make sure, here's what I've done: I cloned the whole project and then replaced all instances of 'Stoppable' to 'Pausable'.

Now, How do I run tests for it?

Thanks in advance and sorry for the silly question!

@federicobond
Copy link
Contributor

Hi @JGcarv, thanks for taking the time to contribute to OpenZeppelin.

You should be able to run the tests with npm test after installing all dependencies (npm install) and running an instance of testrpc in another console.

testrpc is installed with npm install -g ethereumjs-testrpc

@JGcarv
Copy link
Contributor

JGcarv commented Jan 31, 2017

Hey @federicobond , thanks for the reply!

So, I installed the dependencies and ran the tests(which were all passing) but when I tried to git push origin myBranch I got the following message:

remote: Permission to OpenZeppelin/zeppelin-solidity.git denied to JGcarv. fatal: unable to access 'https://github.com/OpenZeppelin/zeppelin-solidity.git/': The requested URL returned error: 403

Do you have any idea what it might be? Thanks!

@federicobond
Copy link
Contributor

Yes, you cannot push directly to the OpenZeppelin fork because you are not a collaborator. You should make your own fork on GitHub and configure your local clone to push there, like this:

git remote rename origin upstream
git remote add origin git@github.com:JGcarv/zeppelin-solidity.git

Once you do that, you will be able to push your branch:

git push -u origin myBranch

If you want to pull updates from the official fork later, you can then do so like this:

git pull upstream master

@JGcarv
Copy link
Contributor

JGcarv commented Feb 1, 2017

Yeah, that makes sense.

Anyway, I followed the steps and made a new pull request. Let me know if things do work out.

Also, thank you for your patience!

@maraoz
Copy link
Contributor Author

maraoz commented Feb 17, 2017

Great work @JGcarv, closing this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Low hanging fruit for new contributors to get involved!
Projects
None yet
Development

No branches or pull requests

3 participants