ci/cd script to shellcheck .sh files and make sure they're executable as
part of cicd so it fails loud with the specific problem if Permissions
Issue 2 The Revengeance happens again
Re-creation of https://github.com/Aurorastation/Aurora.3/pull/21046 to
skip merge conflict hell. Brings us modern TGUI.
**ALTERNATE TITLE: TGUI HELLSCAPE PR
ABANDON ALL HOPE YE WHO ENTER HERE**
- [x] Migrate build tools (javascript -> typescript, bun for package
management).
- [x] Upgrade all TGUI dependencies and associated root files to
TG-congruent versions (axios, babel, dompurify, eslint, highlight,
marked, prettier, sass, source-map, stacktrace-parser, typescript).
- [x] InfernoJS -> React migrations
- [x] React cleanup and polish (migrate all remaining .js files to
appropriate .ts or .tsx filetype, all remaining hooks, linting, error
corrections, etc.)
- [ ] Test all remaining TGUI interfaces
# Summary
This PR updates the CI check running on labels like 'changes required'.
## Changes
- Refactors DNM CI check to run on merge queue events only instead of
open PRs to avoid confusion on the state of the PR code-wise.
This is an iteration of #22436
# Summary
This PR updates the CI check running on labels like 'changes required'.
## Changes
- Refactors DNM CI check to run on merge queue events only instead of
open PRs to avoid confusion on the state of the PR code-wise.
# Summary
This PR refactores code and structure of the current persistence
subsystem, in preparation for Persistency: Circles, Squares and
Triangles.
This should not contain any user facing changes.
~~This PR is based of branch #21925 and **needs** to be merged in order.
The files changed display will be meaningless until then.~~ *Done.*
## Changes
- Split subsystem in partial files.
- Refactored proc names, added "persistentObject" format for current
code.
- Renamed SQL table.
- Refactored logging and call hiearachy.
- Fix CI labeler adding DB label on non-SQL files.
NUFC
Discovered this being an issue when I checked our pulse, and noticed
this running on _every single fork._
Signed-off-by: Cody Brittain <1779662+Generalcamo@users.noreply.github.com>
This has zero reason to exist in our code base. We have no procs or
variables tied to this. I removed it to make future modifications
cleaner.
---------
Signed-off-by: Cody Brittain <1779662+Generalcamo@users.noreply.github.com>
- The Set Odyssey Type verb now properly works, and can be used as soon
as the lobby starts.
- Administrators can now manually change Odyssey canonicity.
---------
Co-authored-by: Matt Atlas <liermattia@gmail.com>
This PR updates the repo fully to Byond 516.1673. We now have access to
Associative Lists, Vectors, Matrices, and a huge number of math
improvements tha will allow us to catapult the repo into a new era of
simulationism.
I have tested this PR to verify that it works.
<img width="1076" height="1079" alt="image"
src="https://github.com/user-attachments/assets/c69a7276-7611-4a59-8630-46d8dd8a12a6"
/>
# Summary
This PR removes the already checked-in build artifacts generated from
the TGUI build stage.
This should prevent further merge-conflicts and confusion about file
changes that have not been made by the user.
## Changes
- Remove already checked-in TGUI bundle files listed in gitignore.
- Removed manually executed workflow for TGUI update, responsible for
re-adding auto-generated files.
<img width="190" height="311" alt="image"
src="https://github.com/user-attachments/assets/a2e1aaf1-13a6-45df-858a-765e7dd66af1"
/>
# Summary
This PR updates the triage bots schedule and raises the
operations-per-run limit.
# Details
Previous actions have been implemented using a defensive approach to
test the bots runtime and rate limits.
At the moment the single run at 6 in the morning utilized `0,0066`% of
our hourly GitHub API rate limit.
With those settings we will be done with the currently open 800 issues
in ~1/3 year.
This PR updates the schedule to hourly and raises the API limit to 100
(3x of the default, out of 4500 API calls per hour, based of the stale
action execution log).
- Hourly will make the bot much more responsive (after the 800 issues
have been ~~purged~~ processed).
- A higher rate will allow the current state to be processed faster and
will provide better response to higher workloads in the future.
- The cache continues to handle any workload above 100
operations-per-run.
# Summary
This PR adds the missing actions write permission to the triage bot.
# Details
The actions write permission is required to access the actions cache
that is needed for operations-per-run continuity. This one was simply
missing.
# Summary
This PR fixes the to-be exempt labels on issues and PRs that the stale
action should ignore when trying to mark them as stale.
# Details
The label exempt regex syntax isn't supported [anymore?], this resulted
in the setting being ignored.
This PR also contains light cleaning, removal of defaults, update of
cron to daily to utilize the rate limit per run without getting rate
limited.
# On merge
Please trigger the action manually on merge so the output is immediately
available to verify the fix.
The documentation provides no info on the formatting of the labels
within their comma brackets, it might be possible they have another
format in code (e.g. `"Bot Ignore"` -> `"bot-ignore"`?).
Not a real breaking behavior if wrong but possibly annoying and open to
fix afterwards.
# Summary
This PR adds a GitHub action workflow to automatically triage issues and
pull requests regarding their activity.
## Intent
The repository features a lot of really old and no longer relevant
issues. Those issues are commonly not maintained by their authors and
processing them manually is not feasible.
By adding this workflow we got a very transparent and user friendly way
to keep the issues clear and meaningful: Issues that will be opened get
more attention and don't drown in the sea of stale issue. Issues marked
as replicable are easier to spot for anyone (developers *and* any other
contributor), making them easier to get picked.
Similar for PRs: I have seen multiple manual clean ups of dead pull
requests. This can be automated as well. For the start, I have opted out
of auto closing PRs, but this can be easily added afterwards if it gains
interest.
Generally, this keeps the repository cleaner, making it easier to
interact with issues posted. This helps anyone looking for an issue to
fix, which is, by my own experience, an easy for new contributors to
start.
## Settings
### Issues
Issues will be marked as stale after 60 days of no activity. If the
issue has been labeled replicable, it won't get marked as stale. Any
activity will remove the stale label again.
After additional 30 days the issue will be closed if its still marked as
stale.
### Pull requests
Pull requests will be marked as stale after 60 days of no activity. If
the pull requests has been labeled by any discussion label, it won't get
marked as stale. Any activity will remove the stale label again.
Pull request will never be auto-closed, unlike issues.
Destroys a ton of sources of lag:
- /obj/machinery/biogenerator/interact and
/obj/machinery/computer/rdconsole/attack_hand
Both of these call REF(src) constantly on their UI update, which also
happens constantly. Death by a thousand cuts
- /obj/machinery/button/ignition/attack_hand and
/obj/machinery/button/switch/holosign/attack_hand
Sleeps rather than timers, iterating the entire machinery list rather
than just storing the IDs we need at roundstart
- /obj/machinery/telecomms/update_icon and /obj/machinery/meter/process
Calling overlay updates WAY TOO MUCH. UpdateOverlays is a significant
overhead for the server at this point and the two of these combined are
responsible for a little over 20% of updates. They now should only
update overlays when necessary rather than every tick.
- NEW! /obj/machinery/disposal/proc/update and
/obj/machinery/portable_atmospherics/hydroponics/update_icon
These two were also offenders, worse than telecomms but better than
meters. They have also been brought into line.
- /mob/living/carbon/slime
Hard-del'd if grinded into slime extract less than two minutes after
being "born". Fixed by adding TIMER_DELETE_ME flag.
---------
Co-authored-by: Matt Atlas <liermattia@gmail.com>
Ported and adapted the code style guideline from TG, with our Aurora
flavoring
Referenced the guidelines from the readme and put a small clarification
on our supported toolchain
Turned a ton of unmanaged globals into managed globals.
Refactored some UT output.
Removed some unused things, including vars.
Added a test to ensure people don't keep adding new unmanaged vars.
Updated runners to ubuntu 2024.04 LTS
Consolidated some node cache utilization in its own action
Updated merge conflict detector action version
PRs with merge conflicts now get the Review Required tag removed, and
PRs that had a conflict get a comment remembering the author to mark
them as ready to review if they are ready once the conflict is resolved
https://forums.aurorastation.org/topic/20198-mission-briefing-auroras-gamemode-revolution
To-do:
- [x] Finish storyteller verbs.
- [x] Storyteller landmarks.
- [x] Proper storyteller spawning. Right now the gamemode system is
happy with just picking one storyteller and no actors.
- [x] Antagonist whitelists code.
- [x] Adding the Storyteller whitelist.
- [x] Mission map loading code.
- [x] Map in a bunch of missions.
- [ ] Storyteller adminhelps.
---------
Co-authored-by: Matt Atlas <liermattia@gmail.com>
Co-authored-by: DreamySkrell <>
# what and why:
byondapi stuff
byondapi is cool
implementation is very heavily inspired by
https://github.com/ParadiseSS13/Paradise/pull/25328
this PR adds a very minimal but usable rust project to the repo
this was test-merged to see if it actually works in game on the live
server
but as it is now the PR does not add any byondapi calls to dm code
---------
Co-authored-by: DreamySkrell <>
