cyberdisc-bot
cyberdisc-bot copied to clipboard
Automatic readme updating
Resolves #413
Would this work without a persistent disk?
Could try just reading from the readme channel itself and then putting it into a JSON format and then comparing maybe I'm not sure I'll have a think tomorrow
Thinking about it I could get the sha-1 of the file locally then use the GitHub API to get the sha of the file on there then compare it
Yeah perhaps, my idea was to pin the hash in the dev testing channel and compare the pinned hash with one calculated at deployment.
If same, nothing happens.
If different, then it removes the previous pin, posts and pins the new hash, nukes the #readme channel and creates it again.
Yh that probs a better idea as I just realised the API one wouldn't work and whats the dev testing channel?
It's an internal channel for testing bot features, but the point is, any channel like this can be used
oh right cool ill do it that way
This should do the trick the only thing it needs changing is the channel id for the dev testing channel
Channel ID is: 543766802174443531
Thanks
Lmk when if this is ready/tested please.
Yh it's ready and tested
Lint issue fixed turns out I was looking at the wrong file should be good to go
Is this ready now?
Yh this is ready for production I've tested it
Shall I make it auto nuke the channel when the push command is called?
Yeah that sounds good
@thebeanogamer @AnonGuy Can we get a review?
Will this ever be merged?
Not unless @thebeanogamer and @AnonGuy can check this out which is an unlikely occurrence.
Ah ok