* Fix git add in DMAPI update action (#54505)
Old command won't add new files. git hard.
* Fix git add in DMAPI update action
Co-authored-by: Jordan Brown <Cyberboss@users.noreply.github.com>
* Clearing my assignment here (#54449)
Because that'd basically be roundabout self-merging
* Clearing my assignment here
Co-authored-by: Jordan Brown <Cyberboss@users.noreply.github.com>
* Makes changelog compile only fire if CHANGELOG_ENABLER secret is present (#53845)
Not tested yet, so please speak up if you notice anything off.
For any interested downstream/fork maintainers reading this:
You need to add CHANGELOG_ENABLER secret with some nonempty value to your repository if you want this action to continue to work as before.
* Makes changelog compile only fire if CHANGELOG_ENABLER secret is present
Co-authored-by: AnturK <AnturK@users.noreply.github.com>
* Updates the tgs-dmapi-updater action reference (#53777)
* Updates the tgs-dmapi-updater action reference
Co-authored-by: Jordan Brown <Cyberboss@users.noreply.github.com>
* Add workflow_dispatch to TGS DMAPI update action for testing (#53775)
* Add workflow_dispatch to TGS DMAPI update action for testing
Co-authored-by: Jordan Brown <Cyberboss@users.noreply.github.com>
* Merge pull request #53674 from tgstation/Cyberboss-patch-2
Adds a GitHub action to automatically update the DMAPI
* Adds a GitHub action to automatically update the DMAPI
Co-authored-by: Jared-Fogle <35135081+Jared-Fogle@users.noreply.github.com>
* Change BYOND version to 513.1526
* Remove BSQL from docker image
* Add a docker publish action
* Add a docker test action
* Cleanup runtime icons
* Cleanup runtime sounds
* Correct docker workflow names
* Add Dockerfile as an appveyor cache dependency
* Fix build issues
* Copy all dlls
* No need for .dlls in docker
* Minor cleanups
Improves the description of the stale auto issue comment.
About The Pull Request
It is not clear to people how the auto stale process works, and they are having their PR shut because of it.
Some things to note if your PR is autoclosed
A)Preferably, ask a maintainer to reopen the PR, at that point they will decide if your PR was going to be merged and choose to reopen your PR and remove the stale label.
B)Open a new PR with the same branch (less preferred, but fine if you can't get any maintainers attention)
If your PR is marked stale but you have no compile issues or outstanding review, you need to make sure you follow up with maintainers in discord, as it's likely there are outstanding design issues preventing your PR being merged, or no appetite to include the change.
About The Pull Request
Uses actions to automatically rebuild tgui if files are changed, then push the result.
Triggers on push to master, pushes results to master.
Also disables build checking in Travis because it's unimportant now.
About The Pull Request
Clarification that was brought to my attention:
the repo for this action defines it as without activity, so I assume literally any discussion/review is enough to bump and avoid the stale.
Considering this, it may be worth deploying an autocloser on PRs and an autolabeler on issues as well.
As title
Currently configured to mark PRs stale after 7 days. RED LABEL prs are exempt.
DOES NOT autoclose.
This is definitely a shift in how stale PRs are handled so this is a discussion thread at the same time as a pull request.
Message used:
This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being closed by a maintainer if it is not updated or reviews are not addressed. If your PR is closed as stale, feel free to open a new one after dealing with the issues.
