RPCS3/discord-bot
1
0
Fork 0
mirror of https://github.com/RPCS3/discord-bot.git synced 2026-07-19 13:54:44 -04:00
Code Issues 20 Packages Projects Releases Wiki Activity

[GH-ISSUE #546] [Feature Request] Mention if a user is using a known broken build #52

New Issue
Closed
opened 2026-02-15 15:54:48 -05:00 by yindo · 3 comments
yindo commented 2026-02-15 15:54:48 -05:00
Owner
Copy Link
Copy Source

Originally created by @dio-gh on GitHub (Mar 20, 2020).
Original GitHub issue: https://github.com/RPCS3/discord-bot/issues/546

Title is self-explanatory. Obvious limitations are:

  • not knowing until how long builds are broken for
  • bad builds wont be tagged immediately
Originally created by @dio-gh on GitHub (Mar 20, 2020). Original GitHub issue: https://github.com/RPCS3/discord-bot/issues/546 Title is self-explanatory. Obvious limitations are: - not knowing until how long builds are broken for - bad builds wont be tagged immediately
yindo added the enhancement label 2026-02-15 15:54:48 -05:00
yindo closed this issue 2026-02-15 15:54:49 -05:00
yindo commented 2026-02-15 15:54:49 -05:00
Author
Owner
Copy Link
Copy Source

@13xforever commented on GitHub (Mar 21, 2020):

Build status is not tracked anywhere, and if the bot will start this tracking, it would require reimplementing almost the whole update api

@13xforever commented on GitHub (Mar 21, 2020): Build status is not tracked anywhere, and _if_ the bot _will_ start this tracking, it would require reimplementing almost the whole update api
yindo commented 2026-02-15 15:54:49 -05:00
Author
Owner
Copy Link
Copy Source

@HerrHulaHoop commented on GitHub (Mar 21, 2020):

This should ideally be tracked in the website's API. That way the auto-updater and discord bot could both pull the info from the same source and alert the users. Not all RPCS3 users are present on discord. Should work with Ani and possibly open an issue on the Compat list repo.

@HerrHulaHoop commented on GitHub (Mar 21, 2020): This should ideally be tracked in the website's API. That way the auto-updater and discord bot could both pull the info from the same source and alert the users. Not all RPCS3 users are present on discord. Should work with Ani and possibly open an issue on the Compat list repo.
yindo commented 2026-02-15 15:54:49 -05:00
Author
Owner
Copy Link
Copy Source

@dio-gh commented on GitHub (Mar 21, 2020):

Build status is noz tracked anywhere

It is visually noted at least in #build-updates.

@dio-gh commented on GitHub (Mar 21, 2020): > Build status is noz tracked anywhere It is visually noted at least in #build-updates.
yindo changed title from [Feature Request] Mention if a user is using a known broken build to [GH-ISSUE #546] [Feature Request] Mention if a user is using a known broken build 2026-06-05 15:25:05 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Hacktoberfest
Hacktoberfest
bug
enhancement
enhancement
enhancement
fun stuff
good first issue
good first issue
help wanted
high priority
invalid
log analyzer
pull-request
Mirrored from GitHub Pull Request
 questionable
questionable
wontfix
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: RPCS3/discord-bot#52
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?