tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 14:05:37 +02:00
Code Issues Projects Releases Wiki Activity

DOCS Per-project issue tracking shortcut (#9554)

Browse Source
This commit is contained in:
Ingo Schommer 2020-07-29 16:13:21 +12:00 committed by GitHub
parent 8287fad24d
commit 4a45338c6a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 23 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/en/05_Contributing/00_Issues_and_Bugs.md
View File

@ -62,3 +62,25 @@ read our guide on [how to write secure code](/developer_guides/security/secure_c
* [forum.silverstripe.org](http://forum.silverstripe.org): Forums on silverstripe.org * [forum.silverstripe.org](http://forum.silverstripe.org): Forums on silverstripe.org
* [All issues across modules](https://www.silverstripe.org/community/contributing-to-silverstripe/github-all-core-issues) * [All issues across modules](https://www.silverstripe.org/community/contributing-to-silverstripe/github-all-core-issues)
## Identifying issues and pull request relevant to your own project
Our [issue browser](https://silverstripe-github-issues.now.sh/) can be helpful to identify known issues and pending pull requests in
[supported modules](https://www.silverstripe.org/software/addons/silverstripe-commercially-supported-module-list/).
But you're usually only running some of these modules, and others
from the [wider module ecosystem](https://addons.silverstripe.org).
In order to only show issues and pull requests relevant to your project,
we've written a little [composer utility](https://github.com/silverstripe/silverstripe-github-issue-search-composer-util)
which inspects your own `composer.lock` file dependencies,
and searches across all Silverstripe modules in there.
After [installing the composer utility](https://github.com/silverstripe/silverstripe-github-issue-search-composer-util),
use this command to pass through a lock file, and get a URL to open in your favourite browser.
```
cat /my/project/composer.lock | ss-issue-search get-url
```
Protip: You can further filter to certain [issue labels](code#labels)
such as `label:impact/high` to make the results more relevant.

2
docs/en/05_Contributing/01_Code.md
View File

@ -122,7 +122,7 @@ If your change is particularly significant, it may be referred to the [forum](ht
A core committer will also "label" your PR using the labels defined in GitHub, these are to correctly classify and help find your work at a later date. A core committer will also "label" your PR using the labels defined in GitHub, these are to correctly classify and help find your work at a later date.
#### GitHub Labels #### GitHub Labels {#labels}
The current GitHub labels are grouped into five sections: The current GitHub labels are grouped into five sections: