Automate issue creation of new TG API releases #4736
Replies: 3 comments 3 replies
-
|
Just to be sure that I understand correctly, your suggestion is to automate the creation of the issue that a new bot api version exists. |
Beta Was this translation helpful? Give feedback.
-
|
Correct. One of those #4677 |
Beta Was this translation helpful? Give feedback.
-
|
Hi @aelkheir thank you very much for your interest. To be honest, my first thought when reading your description was: https://xkcd.com/1319/ 😄 Which does not mean that it's generally a bad idea and I won't stop anyone from spending time on a neat little automation 🙃 However, I wouldn't personally put this on any PTB roadmap.
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you for giving it a thought 😆 hate that this is very accurate
I gave this a thought, but it would require smb to be active when the new api is released. which is not a bad requirement, especially if the action existed inside ptb, as only the person creating the central branch would just have to remember to trigger it. however, another major motivation for this is that I want the issue to be created before actual work is started on work items. It rarely happens (e.g in recent api update. message) that work would start before the issue creation, which means that people from outside wishing to to contribute would have to see commits to figure out which items have been taken and which available. or ofc ask in dev chat.
Good point. As a compromise it occurred to me to have the action running on schedule, but only send the MD content in a channel (and another mini bot) then to be copy/pasted by someone. this can
but at this point i think i'm nearing the xkcd, for such a small task. i'll rethink it and post here if there're any updates. |
Beta Was this translation helpful? Give feedback.
-
|
tbf I'm pretty sure AI can do this very well. We can just feed it the bullet points from the TG API page, and then ask it to write it in the style of our releases by providing it the markdown of one of the previous releases. Could technically be automated by running a python script which parses the tg api page, and then if there's an update, query any LLM (local ones should also be pretty good), and then either make a github issue or just send a message on telegram. obviously all that is much more work than just manually doing it once every few months imo |
Beta Was this translation helpful? Give feedback.
-
|
ha, seems like i forgot Ai exists. agree if we're not automating the issue creation itself, AI is much simpler. previously (while a contributor) doing it manually used to take me a good while b/c github wouldn't allow me to access the MD of previously closed issues (ones i created) which is no longer the case. so my root problem is solved now. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Although new api releases come fairly apart, it is still a daunting task to set up the issue template with new updates and instructions for new contributors.
I've been thinking of ways to automate the process. Something like this:
create_new_api_issue.pyscript that extracts the new items, prepares them with contributing instructions and submits the issue.some new api releases don't require major code changes (only version bumps), but still the issue can be used to track those.
Having the action inside of ptb might be out of scope (?). In that case, telegram-bot-api-changes could be extended to include it, or i can have it in my personal account
Would you be okay with an automated issue, assuming it works error free?
If yes, and you like the idea, @Bibo-Joshi do you think it fits to exist in the telegram-bot-api-changes repo or if also out of scope i can have it under my account.
Beta Was this translation helpful? Give feedback.
All reactions