-
Notifications
You must be signed in to change notification settings - Fork 215
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 naming rules to contributing #1291
Conversation
✅ Deploy Preview for dlt-hub-docs canceled.
|
* **exp** - an experiment where we are testing a new idea or want to demonstrate something to the team, might turn into a feat later (ticket encouraged) | ||
* **test** - anything related to the tests (ticket encouraged) | ||
* **blogs** - a new entry to our blog (ticket optional) | ||
* **docs** - a change to our docs (ticket optional) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also maybe we can add infra
for things related to CI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we also add refactor
scope?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
CONTRIBUTING.md
Outdated
|
||
#### Ticket Numbers | ||
|
||
We encourage you to attach your branches to a ticket, if none exists, create one an explain what you are doing. For feat and fix branches, tickets are mandatory, for exp and test branches encouraged and for blogs and docs branches optional. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
create one *an*
-> and
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and maybe enclose feat/fix in backticks
Description
We want to add some rules how to name stuff (mostly branches). Let's discuss :)