Direct link to plugin removal

[zbynek]

Following jenkins-infra/update-center2#299 it might be easier to point directly to the file that needs editing.

CC @daniel-beck

[jenkinsadmin]

Build failed; the context from the latest run is:

Expand to view

[2019-09-16T20:42:48.637Z] Pull request #2485 opened
[2019-09-16T20:42:48.639Z] Connecting to https://api.github.com using jenkinsadmin/****** (GitHub access token for jenkinsadmin)
[2019-09-16T20:42:49.477Z] Connecting to https://api.github.com to check permissions of obtain list of zbynek for jenkins-infra/jenkins.io
[2019-09-16T20:42:49.674Z] Loading trusted files from base branch master at 5680006a478a99639339ac6b0d2a2450709d8d9e rather than a141556bd87b38060f3c13ec5c6a4f10765f965d
[2019-09-16T20:57:35.326Z] 
[2019-09-16T20:57:35.326Z] GitHub has been notified of this commit’s build result
[2019-09-16T20:57:35.326Z] 
[2019-09-16T20:57:35.333Z] java.lang.OutOfMemoryError: Java heap space
[2019-09-16T20:57:35.333Z] Finished: FAILURE

Powered by the Comment Logger

[daniel-beck]

Would rather link to the section in the readme to be more stable in case of changes.

I wonder whether it's possible to have stable anchors in Markdown so it would also resist a change of the section title.

[zbynek]

@daniel-beck makes sense. The Readme is linked in the next sentence anyway, so maybe we can reduce it to just one link (see my last commit).