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

Add CONTRIBUTING.md and improve readme #928

Merged
merged 8 commits into from
Jul 18, 2019
Merged

Add CONTRIBUTING.md and improve readme #928

merged 8 commits into from
Jul 18, 2019

Conversation

sohkai
Copy link
Contributor

@sohkai sohkai commented Jul 18, 2019

Fixes #370.

Also adds few notes on the branching strategy, as well as some developing and contributing notes.

@auto-assign auto-assign bot requested a review from bpierre July 18, 2019 10:29
Copy link
Contributor

@bpierre bpierre left a comment

Choose a reason for hiding this comment

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

❤️

1. Celebrate your success after your pull request is merged!

It's OK if your pull request is not perfect (no pull request is).
The reviewer will be able to help you fix any problems and improve it!
Copy link
Contributor

Choose a reason for hiding this comment

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

Nice 👌


## Styleguide and development processes

For the frontends, we use [prettier](https://prettier.io/) and [eslint](https://eslint.org/) to automatically lint and format the project.
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we could add that we generally have a npm run lint task to run ESLint with the right configuration, and that we generally provide a .eslintrc and a .prettierrc file (not strictly the case everywhere, but it’s easy to fix)?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done in 499d93c.

README.md Outdated

Developing the frontends locally can be a bit tricky, due to the frontends' reliance on a properly configured Aragon client.

For now, you can follow [@bpierre's gist](https://gist.github.com/bpierre/22572415b90577aa17e5953fa68980eb#developing-the-apps) to start an app's local frontend server and connect it to a locally running Aragon client.
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we start to move this in every frontend-related repository, with a name like CONTRIBUTING_FRONTEND.md or QUICKSTART_FRONTEND.md, even if it’s still incomplete?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think we can keep in the CONTRIBUTING and point people to it, perhaps if it's still hard to find we can move it to its own file 😄.

I've also added it in aragon/aragon: aragon/client#880.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 98.0% when pulling 06c83eb on readme into ed4c040 on master.

@sohkai sohkai merged commit 07c54da into master Jul 18, 2019
@sohkai sohkai deleted the readme branch July 18, 2019 15:08
ramilexe pushed a commit to ConsiderItDone/aragon-apps that referenced this pull request Dec 9, 2021
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.

[META] Create CONTRIBUTING doc for this repo
3 participants