Some suggestions regarding the summaries in no particular order. Some of them have been brought up in review comments before but I'm repeating them here to make it easier to find them.
- Automatically request a review from the person who merged the PR that triggered the push event. Otherwise nobody will be notified.
- Create a label
type/auto-generatedfor easy filtering
- Additionally, use a different tag than
[CI]
- Additionally, use a different tag than
- Move all auto-generated branches into one "folder" of branches, e.g.
auto/summaries/...orsummaries/... - Mark auto-generated files as generated in
.gitattributes - Consider auto-merging the summary PRs through an app or machine user
@iHiD @ErikSchierboom
SaschaMann
All 4 comments
Automatically request a review from the person who merged the PR that triggered the push event. Otherwise nobody will be notified.
Suggest auto-review from @ErikSchierboom as well.
Mark auto-generated files as generated in .gitattributes
What does this do?
Consider auto-merging the summary PRs through an app or machine user
For this we'd need two bots - one to approve and another to merge. (Not stating pros/cons - just thinking outloud)
iHiD
on 25 Jun 2020
What does this do?
Hides them from repo stats and diffs: https://help.github.com/en/github/administering-a-repository/customizing-how-changed-files-appear-on-github
SaschaMann
on 25 Jun 2020
These are all nice suggestions. I'll implement them
ErikSchierboom
on 26 Jun 2020
See #1759
ErikSchierboom
on 26 Jun 2020
Related issues
ErikSchierboom
路
3Comments
efx
路
3Comments
oanaOM
路
6Comments
valentin-p
路
5Comments
tehsphinx
路
7Comments