Skip to content

Commit 9c3eacd

Browse files
authored
Add ticket reference to Depfu setup (#422)
* Add ticket reference to Depfu setup In khw we use ticket references in our Depfu configuration: renuo/khw2#606 I propose that we set the reference by default. * Apply suggestion from @CuddlyBunion341 * Update image link
1 parent f6b6375 commit 9c3eacd

File tree

2 files changed

+12
-3
lines changed

2 files changed

+12
-3
lines changed

images/depfu_pr_title.png

144 KB
Loading

ruby_on_rails/depfu.md

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ dependencies. It will automatically create a pull request to the project
55
if a security vulnerability has been disclosed.
66

77
1. Ask wg-operations to add repository access for Depfu to you new Github
8-
repository.
8+
repository.
99

1010
That's all :-)
1111

@@ -21,8 +21,8 @@ Enable minor engine updates.
2121
be available on their platform, so you may need to delay the upgrade. Check the
2222
following GitHub repositories to see if Heroku added support already:
2323

24-
* <https://github.com/heroku/heroku-buildpack-nodejs>
25-
* <https://github.com/heroku/heroku-buildpack-ruby>
24+
- <https://github.com/heroku/heroku-buildpack-nodejs>
25+
- <https://github.com/heroku/heroku-buildpack-ruby>
2626

2727
## Automatic merging
2828

@@ -55,3 +55,12 @@ jobs:
5555
PR_URL: ${{github.event.pull_request.html_url}}
5656
GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
5757
```
58+
59+
## Ticket reference
60+
61+
In order to avoid searching for the maintenance project after reviewing a Depfu PR,
62+
we add the ticket to the PR title according to the following Depfu configuration:
63+
64+
![Depfu Redmine Ticket PR Title](../images/depfu_pr_title.png)
65+
66+
Make sure that the ticket number matches the actual maintenance ticket.

0 commit comments

Comments
 (0)