mirror of
https://github.com/directus/directus.git
synced 2026-01-27 12:58:03 -05:00
5cf2c0d724
* Point to docs hosted C&C
* Point to hosted contributing guidelines
* Remove outdated information
This is incorrect, so does more harm than good imo
* Update contributing guidelines to add feature requests flow
* Lil nicer to read
* Add missing words to dict
* Update docs/contributing/code-of-conduct.md
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
* Update docs/contributing/introduction.md
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
* Update docs/contributing/pull-request-process.md
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
* Update docs/contributing/feature-request-process.md
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
* Update docs/contributing/feature-request-process.md
Co-authored-by: Kevin Lewis <kvn@lws.io>
* Update docs/contributing/pull-request-process.md
Co-authored-by: Kevin Lewis <kvn@lws.io>
* Fix license/version for new packages (#18536)
* Standardize TSConfig use (#18538)
* Use tsconfig.prod.json in packages
* Use prod tsconfig in api
* Install node types in storage
* Use vitest run instead of --watch=false (#18540)
* Remove local file
* Revert "Use vitest run instead of --watch=false (#18540)" (#18542)
This reverts commit 97f0af669e.
* Setup boilerplate for data (#18541)
* Setup boilerplate for data
* Update readme
* Fix directory link
* Final tweaks from Ben
---------
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
Co-authored-by: Kevin Lewis <kvn@lws.io>
32 lines
2.0 KiB
Markdown
32 lines
2.0 KiB
Markdown
# Pull Request Process
|
|
|
|
Pull Requests (PRs) are a fantastic way to contribute back to the project. It's one of the fastest ways to see a bug fix
|
|
or new feature you care about land in the platform.
|
|
|
|
Reviewing and maintaining community submitted code is a very time consuming process. To ensure the core team can give
|
|
every PR the tender love and care it deserves, and not let valuable PRs go stale, we require that:
|
|
|
|
**Every pull request must be in answer to an existing open [Issue](https://github.com/directus/directus/issues).**
|
|
|
|
We use [GitHub Issues](https://github.com/directus/directus/issues) as a living to-do list of tasks to work on next.
|
|
Each PR resolving a related issue ensures that it aligns with the core team's planning and long-term goals. Please leave
|
|
a comment on the issue related to your PR so you can be marked as the assignee. This ensures no one else will
|
|
accidentally work on the same issue at the same time.
|
|
|
|
## Choosing What to Implement
|
|
|
|
We welcome PRs for any [Issue](https://github.com/directus/directus/issues). Issues labeled
|
|
["Community"](https://github.com/directus/directus/issues?q=is:issue+is:open+label:Community) have been identified as
|
|
good improvements or fixes for community members, as they're often a little more scoped in what they affect. This in
|
|
turn makes it easier to implement the change and review the work. Issues labeled
|
|
["Good First Issue"](https://github.com/directus/directus/issues?q=is:issue+is:open+label:%22Good+First+Issue%22) are
|
|
typically easier to resolve for those who haven't contributed to the codebase before, and are therefore a great starting
|
|
point.
|
|
|
|
## Implementing an Accepted Feature Request
|
|
|
|
If you're looking to implement a feature request that hasn't been converted to an issue yet, please contact the core
|
|
team through a comment on the feature request before starting work. There's probably a good reason it isn't
|
|
ready-to-be-implemented yet (unknown timelines, conflicts with other projects, blockers, etc). By collaborating early,
|
|
we ensure your PR can be merged as efficiently as possible!
|