Use NodeJS 14 for update packages workflow
Install npm2rpm globally before bump_rpm
Handle updating nodejs packages
don't install recommends when installing packages
Right now, this saves only two tiny packages (git-remote-gcrypt, nocache),but makes the execution more future proof if any of the packages getrecommends added that we do not need.
Bump peter-evans/create-pull-request from 4 to 5
Bumps [peter-evans/create-pull-request](https://github.com/peter-evans/create-pull-request) from 4 to 5.- [Release notes](https://github.com/peter-evans/create-pull-request/releases)- [Commits](https://github.com/peter-evans/create-pull-request/compare/v4...v5)...
ensure discourse posts have an unique title
otherwise flagging them as "solved" will error out with
Started POST "/solution/accept" for 172.17.0.1 at 2023-01-23 13:17:05 +0000 Processing by DiscourseSolved::AnswerController#accept as */* Parameters: {"id"=>"108249"}...
update our actions
add dependabot config to update our actions automatically
Only run package bumping on theforeman
Otherwise forks also run the same, which is wasting a lot of resourcesand sending failure messages to Discourse.
use github not env context to get run details
The `env` context only has access to custom environment variables (aka: those we set ourself), not the ones provided by GH. For those we need to go and poke at the `github` context.
View revisions
Also available in: Atom