Go to file
James Pace c9ba39f820 Either 200 or 202 is actually fine. 2023-02-15 20:47:52 -05:00
j7s_branch_trigger Either 200 or 202 is actually fine. 2023-02-15 20:47:52 -05:00
Dockerfile Add deployment Dockerfile. 2023-02-14 23:05:52 -05:00
LICENSE All the homies like some docs. 2023-02-14 21:04:27 -05:00
README.md Change default branch. 2023-02-14 23:14:35 -05:00
pyproject.toml Either 200 or 202 is actually fine. 2023-02-15 20:47:52 -05:00

README.md

j7s-branch-trigger

Occasionally checks the state of branches on a provided repo using git remote ls.

If the "branches of concern" have updated since it last looked, it will send a POST to a web hook. The "branches of concern" are defined using a configured web hook.

Configuration

Configuration is done through the following environment variables which are checked at start up.

  • J7S_REPO - Required the url of the repo to check in the format you would hand git clone.
  • J7S_URL - Required the url to post to if a change is seen.
  • J7S_HISTORY_FILE - Default: '/tmp/branch-history.json' the location to save the last seen state.
  • J7S_PATTERN - Default: '^HEAD$' python flavored regex to find branches of concern, for specific branch use '^refs/heads/branch$'
  • J7S_LOOPTIME - Default: 1.0 minutes between checks of the state of of the repo