Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose an endpoint to trigger a repository fetch #7

Open
nlewo opened this issue Mar 3, 2024 · 2 comments
Open

Expose an endpoint to trigger a repository fetch #7

nlewo opened this issue Mar 3, 2024 · 2 comments

Comments

@nlewo
Copy link
Owner

nlewo commented Mar 3, 2024

In order to avoid wating for the next trigger, it would be nice to add a way allowing users/CIs to trigger a fetch.

(Note this has been actually already drafted but removed because i didn't use it.)

@colemickens
Copy link

Additionally, if you use the right headers (E-Tag, I think), you can poll GitHub somewhat rapidly, without exhausting quota. It's a nice option for those who might not have permissions to admin webhooks.

@devzero
Copy link

devzero commented Mar 19, 2024

I'm looking at implementing something using websocat or sockethook so that you can listen to a forge's webhook and expose that as a websocket that machines that can't expose ports can still get near-realtime triggering without having to poll a server

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants