This repository has been archived by the owner on Oct 27, 2022. It is now read-only.
Write a contributing guide for project #6
Assignees
Labels
Comments
Bumbleblo
added
enhancement
|
How it was decided in #4 the repository language will be English for github and portuguese to documents. |
|
We (@Bumbleblo, @joaorobson and @ViniciusBernardo ) talked on slack and we think that #n-name-of-issue is a good pattern for branch names and @joaorobson suggested to abbreviate names when possible, I agree with him. |
Bumbleblo
added a commit
that referenced
this issue
Mar 23, 2019
Signed-off-by: bumbleblo <bumbleblo2013@gmail.com>
Bumbleblo
added a commit
that referenced
this issue
Mar 23, 2019
Signed-off-by: bumbleblo <bumbleblo2013@gmail.com>
Bumbleblo
added a commit
that referenced
this issue
Mar 23, 2019
Signed-off-by: bumbleblo <bumbleblo2013@gmail.com>
Bumbleblo
added a commit
that referenced
this issue
Mar 30, 2019
Signed-off-by: bumbleblo <bumbleblo2013@gmail.com>
|
@Bumbleblo, vc se esqueceu de marcar quais tasks foram concluídas. |
|
Relacionada a #34 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Write a initial contributing guide for our project. That document will contain some sections about how contributing, branch creation rules, issues proposals.. etc.
Tasks
Write that sections in a initial version
Additional Information
Most part of the open source projects in github don't have a contributing guide, so I do not have a good contributing guidelines to inspire. I'll proposal some organization similar with Atom Guidelines
The text was updated successfully, but these errors were encountered: