« first day (1701 days earlier)   

01:25
!!/status
@Ginger I am stargazing. I love ogling the stars.
ok then
[Golem ⚙] petpet.gif
 
11 hours later…
12:24
!!/status
@Ginger: both bots are dead I'm pretty sure
seems it
12:38
wait
the bridge is relaying messages here on discord
guessing the login token expired
so it's able to read messages but not post them
@Themoonisacheese one moment
connection timeout for both, this is your fault
lyxal pushed a commit to Vyxal/v3-new-3.5-ideas in Vyxal/Vyxal: I hate base conversion
This is a true and accurate statement I agree with
12:55
[lyxal ♦️] base conversion :weirdchamp:
or possibly it's chat's fault! who knows
lyxal pushed a commit to Vyxal/v3-new-3.5-ideas in Vyxal/Vyxal: Haters will hate, but this is peek head (and peek tail too)
I fr thought that said "Mocking complex numbers"
@Ginger last night i had a weird internet issue, i thought it was localized to my PC but it seems it's around the same time the bots stopped saying anything, so might be related
[the cat] hm
13:16
lyxal pushed a commit to Vyxal/v3-new-3.5-ideas in Vyxal/Vyxal: The funny haha slicing things with the funny looking faces
lyxal pushed a commit to Vyxal/v3-new-3.5-ideas in Vyxal/Vyxal: Thanks computer for not saving that before committing
lyxal pushed a commit to Vyxal/v3-new-3.5-ideas in Vyxal/Vyxal: Update NewElements.scala
lyxal pushed a commit to Vyxal/v3-new-3.5-ideas in Vyxal/Vyxal: Silly little impl detail
lyxal pushed a commit to Vyxal/v3-new-3.5-ideas in Vyxal/Vyxal: Docy docs for the funny z chars
lyxal pushed a commit to Vyxal/v3-new-3.5-ideas in Vyxal/Vyxal: Update NewElements.scala
lyxal pushed a commit to Vyxal/v3-new-3.5-ideas in Vyxal/Vyxal: special casing
gingershaped closed pull request #2133 (Minor updates) in Vyxal/Vyxal
gingershaped reopened pull request #2133 (Minor updates) in Vyxal/Vyxal
13:41
@Ginger no
ok then
I think there's been minor updates that have had to be reverted
because they broke stuff
so what's the difference between a human merging and VB merging, if the broken stuff only appeared after the merge?
A human merging means someone is available to fix things right away :p
I wouldn't be so sure
clearly what we need to do is make VB sapient
!!/status
13:44
alternatively, figure out how to get github workspace ai thing connected
I tried using it once for a PR
@Ginger I am doing your neighbourhood.
@lyxal true
hey you should uh. autolabel
@lyxal the app didn't have org permissions
!!/help "autolabel add"
`!!/autolabel add (ENUM type: linked_issue/branch_name) (STRING repository) (STRING match) (STRING label)`: Add an autolabel rule. `linked_issue` rules will find issues linked with "Closed #<number>" and
apply `label` if one has a label named `match`. `branch_name` rules will use `match` as a regex
against the branch name of new pull requests.
that's not meant to be multiline
just a second
13:46
gingershaped pushed a commit to VyxalBot3/main in Vyxal/VyxalBot3: Update webhook handler decorator for non-generator handlers
gingershaped pushed a commit to VyxalBot3/main in Vyxal/VyxalBot3: Replace newlines with spaces in command help
fixed it
!!/help "autolabel add"
@lyxal !!/autolabel add (ENUM type: linked_issue/branch_name) (STRING repository) (STRING match) (STRING label): Add an autolabel rule. linked_issue rules will find issues linked with "Closed #<number>" and apply label if one has a label named match. branch_name rules will use match as a regex against the branch name of new pull requests.
rules on repo name?
(do I vyxal/vyxal or just vyxal?)
no org name
13:47
:+1:
none of the commands take an org name, the bot always operates in our org
!!/autolabel add linked_issue "vyxal" "bug" "PR: Bug Fix"
@lyxal Autolabel rule cm4msz2oe0000137ablohmzng created for repository vyxal.
!!/autolabel add linked_issue "vyxal" "difficulty: very hard" "PR: Careful Review Required"
oh wait I should probably lower() the repo name
13:48
@lyxal Autolabel rule cm4mszllp0001137a4xfnkc66 created for repository vyxal.
!!/autolabel add linked_issue "vyxal" "documentation" "PR: Documentation Fix"
@lyxal Argument label not provided, expected a value of type ArgumentType.STRING.
:facepalm:
@lyxal Autolabel rule cm4mt0dxz0002137ax62x8cf1 created for repository vyxal.
!!/autolabel add linked_issue "vyxal" "good first issue" "PR: Light and Easy"
13:49
@lyxal Incorrect type supplied for argument type; expected FLAG but got STRING
@lyxal Autolabel rule cm4mt1gl30003137aqvvmpmo6 created for repository vyxal.
!!/autolabel add linked_issue "vyxal" "difficulty: easy" "PR: Light and Easy"
@lyxal Autolabel rule cm4mt20l00004137ad1batjp5 created for repository vyxal.
when I use branch_name, does that mean branch with the code in it, or branch the code is going into?
gingershaped pushed a commit to VyxalBot3/main in Vyxal/VyxalBot3: Maybe next time I should fix the errors before committing
gingershaped pushed a commit to VyxalBot3/main in Vyxal/VyxalBot3: Make autolabel rules case-insensitively check the repo name
gingershaped pushed a commit to VyxalBot3/main in Vyxal/VyxalBot3: Fix missing argument error message
branch_name matches the branch that's being merged
or, it should
if it doesn't I'll fix that :p
13:52
!!/autolabel add branch_name "vyxal" "production" "PR: Production Update"
@lyxal Autolabel rule cm4mt4ulm0005137ac810kfae created for repository vyxal.
!!/autolabel add branch_name "vyxal" "version-2" "PR: Version 2 Related"
@lyxal Autolabel rule cm4mt5f6o0006137ah6lqv6ff created for repository vyxal.
oh uh the regex is a full match
!!/autolabel add branch_name "vyxal" "version-3" "PR: Version 3 Related"
13:52
@lyxal Autolabel rule cm4mt5rho0007137aqhka6n5q created for repository vyxal.
I can change that if you want :p
@Ginger wait you said being merged
oh
I uh may have been going off merged into
this is why I added a delete command
it might be best to have it the merged into branch
because, for example, a production update has no way of knowing it's a production update if it's the merged
because it's always version-2 -> production
hmm
I can add a new label type for that
this type was intended for stuff like branches named v3-.* being labeled as v3 PRs
13:55
or make it so that branch_name goes off where the code is going
keep the regex matching
because that could still be useful if someone has a v3-.* branch and then makes a new branch from that
oh yeah that makes sense
hold on
I might go for the night and add some more tomorrow
I think a good chunk of the rules are added now though
so, what do you think of the bot? :3c
I'll let it answer for me
!!/status
@lyxal I am doing my usual routine of sleeping and eating.
13:57
That is in fact what I'll be doing
very clever
gingershaped pushed a commit to VyxalBot3/main in Vyxal/VyxalBot3: Check branch_name autolabel rules against base instead of head
I didn't know you installed the lyxal-cam module into the bot
I will interpret that as enjoying it :p
!!/status tingly
@lyxal I am doing exactwy (˘ᵕ˘) what you think :3 I'm doing.
13:58
I think this is my favorite iteration of the bot
@VyxalBot but what if I think you're doing the opposite of what you think I'm thinking?
didn't think that one through did you
!!/trick upsert "'night" "o/"
@lyxal The group !!/trick has no subcommand named "add". Its subcommands are: delete, upsert
!!/trick upsert "bye" "o/"
@lyxal Trick bye updated.
@lyxal Trick night updated.
that's so much longer than typing bye
13:59
!!/trick upsert "rant" "why upsert and not add like a normal person"
@lyxal Trick rant updated.
@Themoonisacheese but you get the bot response
because upsert both adds new commands and edits existing ones
@lyxal Trick 'night updated.
14:00
oh shit right I was going to implement reactions
!!/'night
@lyxal Parse error: Unexpected toplevel character '
lol
almost like it used to be :p
!!/night
(fr)
@lyxal o/
14:01
bro left then came back because he was mentionned 💀💀
!!/autolabel list
Autolabel rules:
- cm4le10ww0000103p6274x5y3 (branch_name on vyxal): something → cool
- cm4le1vg30001103psdihuqxp (linked_issue on vyxal/nonexistent): ligma → sigma
- cm4le2sjn0002103pdq32mg9e (linked_issue on ): →
- cm4le4ual0000sy0sn87zxlv0 (linked_issue on so then): if there's no docstrings → I'll have to configure them "tomorrow"
- cm4le5r9o0001sy0shfwljyhc (branch_name on **markdown**): →
- cm4msz2oe0000137ablohmzng (linked_issue on vyxal): bug → PR: Bug Fix
- cm4mszllp0001137a4xfnkc66 (linked_issue on vyxal): difficulty: very hard → PR: Careful Review Required
!!/autolabel remove "cm4le10ww0000103p6274x5y3"
@Ginger Autolabel rule cm4le10ww0000103p6274x5y3 deleted.
!!/autolabel remove "cm4le1vg30001103psdihuqxp"
14:02
@Themoonisacheese [lyxal ♦️] I hadn't actually left the first time
@Ginger No autolabel rule exists with that ID.
[lyxal ♦️] I was mentioned before I got a chance to leave
@Ginger Autolabel rule cm4le1vg30001103psdihuqxp deleted.
[lyxal ♦️] This time I came back because of the mention though
!!/autolabel remove "cm4le2sjn0002103pdq32mg9e"
14:03
@Ginger Autolabel rule cm4le2sjn0002103pdq32mg9e deleted.
!!/autolabel remove "cm4le4ual0000sy0sn87zxlv0"
@Ginger Autolabel rule cm4le4ual0000sy0sn87zxlv0 deleted.
!!/autolabel remove "cm4le5r9o0001sy0shfwljyhc"
@Ginger Autolabel rule cm4le5r9o0001sy0shfwljyhc deleted.
!!/batch-operation when
14:04
isn't this the only time you'd have ever needed it
so?
okay, reaction support
oh and
@lyxal do we still need !!/prod
[lyxal ♦️] I mean, probably
[lyxal ♦️] I updated it like two weeks or so ago
[lyxal ♦️] And had to manually it
[lyxal ♦️] Becausen't bot
right, I'll do that first then
[lyxal ♦️] 👍
[lyxal ♦️] I'll be going fr fr this time now
should it uh
automatically merge the pr
14:07
!!/rizz
@Themoonisacheese fanum tax
@Ginger that's probably a very bad idea no?
@Ginger [lyxal ♦️] I'll say no because of branch protection rules
right
[lyxal ♦️] Might be slightly messy
[lyxal ♦️] Anyhow going now no more mentioning lyxal golfing nor asking questions of lyxal golfing for sleep period
14:43
so the question with !!/prod is if I just hardcode its settings
whar
is anythin that hardcoded if changing the thing it refers to (not the hardcoded bit, the actual thing) would be harder than simply changing the variable in the script's source and calling it a day
this was considerably longer to type thatn i expected
it's "hardcoded" if I'm checking it into version control :p
the alternative is putting it in the database, like with pretty much every other feature I've added
so? change it and commit the change realistically how many times per year does the name of the production branch change
14:46
fair enough :p
i guess you do already have a database running yeahj
it mostly bothers me because that attaches the bot to our specific setup as if anyone else will ever use it
maybe I can implement a supplementary config file loader for this
15:07
gingershaped closed pull request #114 (Main) in Vyxal/Sandbox

« first day (1701 days earlier)