Context
We want to allow users to submit their repository to be monitored by the bot, directly from the web interface.
Options considered
Option 1: Open an Issue + GitHub action
- User fills a form → redirects to a pre-filled GitHub issue
- GitHub Action triggered on issue creation
- Requires a GitHub account
- Script parses the issue, extracts the URL, validates it
- Script modifies input.json, creates a branch, opens a PR
- We review and merge
Advantages:
- relatively easy for users
- we control
input.json format and can validate URL in CI/CD
- semi-automatic
Drawbacks:
- needs human review and merge
Option 2: Direct PR on input.json
- User clicks a link → GitHub opens the editor on
input.json
- We review and merge
Advantages:
- open PR directly, no CI/CD or logic
Drawbacks:
- user needs to click "Fork"
- user needs to fill JSON file correctly
- needs human review and merge
Option 3: Dedicated server (or service) as backend
- User fills a form on the web interface
- Form is submitted to a backend server we control
- Server validates the URL, modifies input.json, and opens a PR via GitHub API (or push directly)
- Can be implemented using google forms or formspree
Advantages:
- simplest solution user-wise
Drawbacks:
- still needs an external service
First implementation: Option 1
This requires to setup the complete workflow with input.json and bot structure
Context
We want to allow users to submit their repository to be monitored by the bot, directly from the web interface.
Options considered
Option 1: Open an Issue + GitHub action
Advantages:
input.jsonformat and can validate URL in CI/CDDrawbacks:
Option 2: Direct PR on
input.jsoninput.jsonAdvantages:
Drawbacks:
Option 3: Dedicated server (or service) as backend
Advantages:
Drawbacks:
First implementation: Option 1
This requires to setup the complete workflow with
input.jsonand bot structure