« first day (483 days earlier)      last day (1292 days later) » 
01:00 - 15:0015:00 - 00:00

15:04
ok i will do tmrw bye
!!/night
@pxeger lol
wow cookie
ok who created the gh user vyxal-cookie
¯\_(ツ)_/¯ they just kinda showed up when we started talking about cookies
pxeger did
15:14
At first I as gonna say it sounds like the kind of thing that lyxal would do, and then i realized that its the kind of thing that literally any of us would do. :P
lol
@user I deny these accusations
@AaronMiller ඞ
wait. I know how to figure out who it was!
!!/blame
15:17
@AaronMiller It was lyxal's fault!
well now we know
YES!
ysthakur closed PR #38 (Vyxal/VyxalBotSE) (Vyxal:PyGamer0-cookies → Vyxal:master): cookie
ysthakur pushed a commit to VyxalBotSE/master: cookie (#38)
hyper-neutrino deleted branch VyxalBotSE/PyGamer0-cookies
15:18
@hyper-neutrino cookie
what the fuck
wdym
hyper-neutrino closed PR #37 (Vyxal/VyxalBotSE) (Vyxal:AMiller42-patch-1 → Vyxal:master): `goto` is a very good- *gets interrupted by velociraptors*
NOOOOOO
15:20
hyper-neutrino closed issue #31 (Don't report review comments on PRs, Vyxal/VyxalBotSE)
wait is 2x-1 back?
Apparently
RocketScienc
nice
what the fuck is this starboard
Want me to move them into Trash?
15:22
Aight
well if you want sure idrc
No it's good
cookie
maybe i should just stop reporting stuff; people can just look on github or turn on email notifs lmao
wdym
some of the more important reports are nice, like issues, releases, etc.
15:24
True
Maybe don't report individual commits?
70 cookies
cookies are lit
ysthakur pushed a commit to cookie/cookie: Create crystal.yml
ysthakur pushed a commit to cookie/cookie: Update blank.yml
ysthakur pushed a commit to cookie/cookie: Update cookie.yml
ysthakur pushed a commit to cookie/cooKIEE: COOKIE
ysthakur created branch cookie/cooKIEE
ysthakur opened PR #8 (Vyxal/cookie) (Vyxal:cooKIEE → Vyxal:cookie): COOKIE
hyper-neutrino pushed 2 commits to VyxalBotSE/master. Last commit: Merge branch 'master' of github.com:Vyxal/VyxalBotSE
@hyper-neutrino pulling new changes; I will restart in a few seconds if any updates are available
ok new pushes will no longer be reported
15:30
+1
this does mean there is no way to determine if a PR was merged or closed, but supposedly the response is supposed to contain a merge key or whatever
so i will try to figure out a way to properly report merges
sOMEONE PLEASE APPROVE THIS {pr}9https://github.com/Vyxal/cookie/pull/80 PLEASE>
pxeger closed PR #8 (Vyxal/cookie) (Vyxal:cooKIEE → Vyxal:cookie): COOKIE
1 min ago, by hyper-neutrino
this does mean there is no way to determine if a PR was merged or closed, but supposedly the response is supposed to contain a merge key or whatever
@hyper-neutrino hmm
That's annoying
15:32
ysthakur deleted branch cookie/cooKIEE
yeah well i haven't implemented it yet
or rather
elif action == "closed":
    if data.get("merged"):
        action_text = "merged"
    else:
        action_text = "closed"
hyper-neutrino opened PR #14 (Vyxal/Sandbox) (Vyxal:test → Vyxal:master): Update questions and answers.txt
hyper-neutrino closed PR #14 (Vyxal/Sandbox) (Vyxal:test → Vyxal:master): Update questions and answers.txt
ysthakur opened PR #9 (Vyxal/cookie) (Vyxal:add-code-of-conduct-1 → Vyxal:cookie): Create CODE_OF_CONDUCT.md
ysthakur closed PR #9 (Vyxal/cookie) (Vyxal:add-code-of-conduct-1 → Vyxal:cookie): Create CODE_OF_CONDUCT.md
hyper-neutrino opened PR #15 (Vyxal/Sandbox) (Vyxal:test-2 → Vyxal:master): Create E.txt
hyper-neutrino closed PR #15 (Vyxal/Sandbox) (Vyxal:test-2 → Vyxal:master): Create E.txt
hyper-neutrino opened PR #16 (Vyxal/Sandbox) (Vyxal:test-3 → Vyxal:master): f
hyper-neutrino closed PR #16 (Vyxal/Sandbox) (Vyxal:test-3 → Vyxal:master): f
why is there a CoC for cookie?
cookie
ok it should now report merges vs PR closes properly
15:41
ysthakur created branch cookie/cookieee
ysthakur opened PR #10 (Vyxal/cookie) (Vyxal:cookieee → Vyxal:cookie): cookie
ysthakur merged PR #10 (Vyxal/cookie) (Vyxal:cookieee → Vyxal:cookie): cookie
cookie! :)
ysthakur deleted branch cookie/cookieee
@hyper-neutrino You may also want to only report stuff for Vyxal, Vylight, Sandbox, and VyxalBotSE and manually add repos later on if there are any (which there likely won't). That way, we won't be spammed with "cookie" :P
vyxal-cookie opened PR #11 (Vyxal/cookievyxal-cookie/cookie) (vyxal-cookie:cookie → Vyxal:cookie): i am cookie
or just stop spamming cookie
15:43
ysthakur closed PR #11 (Vyxal/cookievyxal-cookie/cookie) (vyxal-cookie:cookie → Vyxal:cookie): i am cookie
@hyper-neutrino we kooky
@hyper-neutrino I don't think that's a viable or maintainable solution.
@user we cookie
just revoke repo creation rights ffs
It's cookie today, but it'll be something else the next
We Vyxal users are not known for our maturity, so we can't expect the spamming to stop
vyxal users: spam
vyxal bot: also spams
vyxal users: *surprised pikachu*
15:51
lol
Don't worry, I made a special team for discussing cookie
i am sadge
vyxal-cookie isnt in the org
Why? Have a cookie
@AaronMiller Oh yeah, someone needs to invite it
im pretty sure only owners can invite users to the org
@exedraj Can you please invite vyxal-cookie?
16:10
wow lol
!!/make me a cookie
@PyGamer0 Here you go: 🍪
3
yoooo
!!/plz make meh a cookie
@PyGamer0 Here you go: 🍪
@PyGamer0 Added you to the cookie team
!!/please make me a cokie
16:11
@PyGamer0 Here you go: 🍪
cookie
this chat room is a mess lol
an occasionally on-topic mess
um... I don't remember joining this team, but I guess I'm in it now?
16:25
@AaronMiller You're also in this team
Argh, how do I remove a pin on a message that doesn't show up on the starboard?
I do that everyday anyway
Ah, thanks
yeah i just re-pinned, unpinned, unstarred
kekw
 
2 hours later…
18:07
ysthakur deleted branch cookie/add-code-of-conduct-1
ysthakur deleted branch cookie/cookiecookie
@exedraj lol
But seriously, why not?
 
1 hour later…
19:31
ysthakur created branch Vyxal/copy-fbt
20:23
PSA: To run vyxal.py directly, you can do python -m vyxal.vyxal from the top project directory (Vyxal, not vyxal). Doing python vyxal/vyxal.py or python vyxal.py (after cd-ing into vyxal) is no bueno. Also, to run tests, you can do pytest from the same directory instead of doing pytest tests or cd-ing into tests and then running pytest. Y'all probably know this already but just making sure
I didn't. I've been wondering how to run it offline, so thx.
I just found about -m vyxal.vyxal myself, thought I was the only one avoiding the repl entirely because of the import errors lol
 
1 hour later…
21:44
ysthakur opened PR #213 (Vyxal/Vyxal) (Vyxal:copy-fbt → Vyxal:fb-transpiler): Heed (most of) mypy's and flake8's warnings/errors
 
2 hours later…
23:26
This is all very representative of us
Good job everyone
@VyxalBot give me a cookie
Hm
@VyxalBot make me a cookie
@exedraj Here you go: 🍪
Worth it
8 hours ago, by user
@exedraj Can you please invite vyxal-cookie?
@exedraj There we have it folks: the official stance on "cookie" cookie cookie
@AaronMiller Being able to assign vyxal-cookie to stuff would be absolutely poggers
@AaronMiller and so it's one of our accounts?
23:30
I would assume so
It's definitely not pxeger's account
8 hours ago, by pxeger
@user I deny these accusations
CMQ: Should we have more organisation owners?
And if so, who?
hyper's probably reliable enough
I don't think we need anyone else to be an owner though
You're already too trusting with ROs :P
> you should give Owner permissions to a small group of people who will manage the organization account.
Yeah, definitely don't make anyone else owner unless necessary
23:35
Of course
I was just asking if y'all think we should have another org owner
Be
cause rn it's only me and Vyxal bot
@exedraj Probably, just in case you die or get kidnapped or something. :p
Aight I added hyper as org owner
Which is just a formalisation of the fact that they already kinda have ownership because they have the credentials for the Vyxal Bot github account
I also want to add a non-moderator organisation owner
@AaronMiller @user @Razetime @emanresuA I'm considering adding one of you to the organisation owner list
Idk who though
make everyone org owner /s
@exedraj We could fight to the death over the privilege of ownership /s
23:47
@user well the thing is ROs can't really do all that much that's problematic, even in the scope of SE and the vyxal room is somewhat nonessential to the vyxal language's existence
whereas org owner can just delete the whole thing, and while we could easily get a reasonaly recent backup from somewhere it would be a major pain
@hyper-neutrino Btw ~100 spammers to deal with when you have time
01:00 - 15:0015:00 - 00:00

« first day (483 days earlier)      last day (1292 days later) »