actions(update-tools): avoid notifying our outdated deps everywhere

[akinomyoga]

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

In the current main branch, workflow update-tools includes the content of the upstream release notes in the created GitHub Issue. This triggers a notification to every upstream contributor mentioned in the release note. This also creates a cross-reference link to our GitHub issue, which reports that our dependency is not up-to-date, in every issue and pull request in the upstream. The information that we need to update our dependency is not relevant to the upstream contributors, issues, and pull requests at all. We should avoid this situation.

In addition, this project has thousands of forks, and all the fork repositories that enabled GitHub Actions do the same at the same time, i.e., an upstream contributor receives several tens of notifications from fork repositories, and an upstream issue receives several tens of cross-reference links to fork repositories. We should have avoided this situation, but it's kind of too late. Even if we update the workflow specification in this repository, the workflow of the fork won't be updated unless the fork pulls our latest commit. We need to ask all these 54 fork repositories currently generating notifications one by one. Anyway, we should still consider updating our workflow to prevent future forks from starting to create an even larger number of notifications to the upstream contributors and issues.

First, we do not need to include a copy of the upstream release note. We can just put a link to the upstream release note. Currently, we anyway hide the content in the <details> tag and require the reader to press the button. The user experience is not so different from pressing a link and visiting the upstream release note.

GitHub issue reference: #7706
Jira reference number [AR-9999]

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

I have run the workflow in my fork repository:

https://github.com/akinomyoga/armbian-build/actions/workflows/update-tools.yml

and observed the results:

https://github.com/akinomyoga/armbian-build/pulls

Checklist:

Please delete options that are not relevant.

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas: This change essentially removes the code, so there is no new hard-to-understand part.
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules: This change is unrelated to any dependency.

[akinomyoga]

@dtolnay @cyqsimon @mr-toolcraft I created a PR for #7706. We should refrain from leaving further comments directly in #7706 as it would be broadcast to all the people mentioned in the original release note, so let's discuss anything related to #7706 here.

[akinomyoga]

@ColorfulRhino Could you also review this as the original author of the workflow?

[igorpecovnik]

Apologize for the noise / spam. I realize now how this is not good. Thank you for the tip and PR!

[igorpecovnik]

Agree.

[akinomyoga]

Thanks!