[FEATURE] Implement GitHub Issue reporter

[swimmwatch]

Is your feature request related to a problem? Please describe.

Currently, webchanges supports a variety of reporters (e.g., email, Pushbullet, Discord), but there is no built-in option to create a GitHub Issue automatically when a page changes.
This limits integration in GitHub-based workflows where issue tracking is preferred over messaging or notifications.

Describe the solution you'd like

I would like to propose adding a new reporter that automatically creates a GitHub Issue when a change is detected.
This reporter would use GitHub's REST API and allow users to specify repository, title format, and issue body template.

A working prototype of such a reporter already exists and can be found here:
Example implementation (hooks.py)

Describe alternatives you've considered

• Using existing reporters (e.g., email or Discord) and setting up external automation to create GitHub Issues manually
• Writing a custom script that wraps around webchanges output and triggers issue creation externally

These options are less integrated and require more setup, which goes against the philosophy of having self-contained reporters.

Additional context

The proposed reporter could accept GitHub authentication via personal access token or GitHub Actions environment variables.
It would be especially useful for projects already hosted on GitHub and looking to track web changes as part of their CI/CD or monitoring pipeline.

[mborsetti]

Sounds interesting, thanks for proposing it!

I will look into it more when I have time.

[swimmwatch]

@mborsetti hi!

Great! I’m happy to prepare a pull request with an initial implementation of this reporter, based on the prototype I mentioned.
This way we can discuss the details in code and adjust it to fit webchanges’ style and requirements.

[mborsetti]

Hi Dmitry, Thanks for the offer, and for contributing the code! I've already jumped the gun and incorporated it last night into a version that's about to be finished (I need to edit the documentation, which has largely already been written). Would you mind to take a look at it once I've polished it over the next few days? Once again, THANKS!

…

On Sun, Aug 10, 2025, 23:49 Dmitry Vasiliev ***@***.***> wrote: *swimmwatch* left a comment (mborsetti/webchanges#105) <#105 (comment)> @mborsetti <https://github.com/mborsetti> hi! Great! I’m happy to prepare a pull request with an initial implementation of this reporter, based on the prototype I mentioned. This way we can discuss the details in code and adjust it to fit webchanges’ style and requirements. — Reply to this email directly, view it on GitHub <#105 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGLWC7Z62W2CEQ5UIPU5AQD3NA4HTAVCNFSM6AAAAACDILQ7L2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZTGQ2TSMBSHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[swimmwatch]

@mborsetti Sure! I’d be happy to take a look once the PR is ready.
Just let me know when it’s up, and I’ll review and test it.

[swimmwatch]

@mborsetti Hi! How’s the development going? Is there anything I can help with?

[mborsetti]

Hi @swimmwatch thanks for the ping, and especially the code, really appreciated!

I've had time to incorporated it, but haven't had time to do any testing or write the documentation. If you can help, I can push an interim branch.

[swimmwatch]

@mborsetti ok! 👌

[mborsetti]

@swimmwatch

Sorry for the delay; it's been quite busy.

Your code has been folded in 3.31.1 (thanks!) as the alpha reporter github_issue, and the default config is:

'github_issue': {
    'enabled': False,
    'token': '',
    'owner': '',
    'repo': '',
    'title': '',
    'labels': [],
    'format_dt': '',
    'format_content': '',
    'assignees': [],
    'type': '',
    'milestone': '',
}

If you can test it would be great; if you have any testing to contribute even better, same for documentation!

Thank you so very much!!

[swimmwatch]

@mborsetti
Thanks for folding it into 3.31.1! I’ll test the github_issue alpha reporter and will aim to add tests and documentation soon.

[mborsetti]

Hi @swimmwatch,

Have you had some time to test?

Thanks

[swimmwatch]

Hi @mborsetti
Sorry for the late reply — I’ve been swamped with work.

I built a GitHub Action that uses your project:

• https://github.com/swimmwatch/webchanges-action

I’m also using this Action in a couple of my repos:

• https://github.com/swimmwatch/vk-mini-app-auth
• https://github.com/swimmwatch/telegram-webapp-auth

In these projects I periodically check for updates to the Telegram/VK Mini Apps documentation. If there are changes, a GitHub Issue is created automatically. Creating issues via webchanges works great with no problems.

Thanks for the awesome project! If you think it’s useful, feel free to mention the Action in your README—I’d love any feedback.