You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When there is no news, the new CI bot simply asks to include a news file using news/TEMPLATE.rst.
The current comment lacks (1) good examples, (2) the new practice of No news: .., and (3) doesn't guide where to place the news under, etc. changed, fixed, etc. This isn't a big deal for us (BG group) since we have a separate GitLab page but it might be a source of confusion for those adopting our current cookiecutter and new contributors contributing to their cookiecuttered packages.
Proposed solution
In the bot comment, improve wording and add a link to the section in the cookiecutter doc once deployed:
The text was updated successfully, but these errors were encountered:
bobleesj
changed the title
feat: better guide new user in news CI news bot command by
feat: better guide new user in CI news bot warning comment
Dec 31, 2024
bobleesj
changed the title
feat: better guide new user in CI news bot warning comment
refactor: better guide new user in CI news bot warning comment
Dec 31, 2024
bobleesj
changed the title
refactor: better guide new user in CI news bot warning comment
refactor: Better guide new user in CI news bot warning comment
Jan 2, 2025
Problem
When there is no news, the new CI bot simply asks to include a news file using
news/TEMPLATE.rst
.The current comment lacks (1) good examples, (2) the new practice of
No news: ..
, and (3) doesn't guide where to place the news under, etc.changed
,fixed
, etc. This isn't a big deal for us (BG group) since we have a separate GitLab page but it might be a source of confusion for those adopting our current cookiecutter and new contributors contributing to their cookiecuttered packages.Proposed solution
In the bot comment, improve wording and add a link to the section in the cookiecutter doc once deployed:
The text was updated successfully, but these errors were encountered: