0mega/fourth-wall

Pull request and build status monitor

Fourth Wall

Pure client-side pull request and build status monitor for Github repositories.

How to use

The project is hosted through Github pages: http://alphagov.github.io/fourth-wall/?token=_token_&gist=_gist_id_

You will need to have a Github API token with access to the relevant repositories if you don't already have one. To do that, visit https://github.com/settings/applications and create a new personal access token. To use the team parameter you will need to give the token the read:org permission.

The following query parameters are required:

• token: Your Github API token

At least one of:

• gist: ID of the Gist containing the list of repositories to monitor.
• team: Github organisation and team name to build the list of repositories in the form {org}/{team} (requires the read:org permission).
• team[]: Given multiple times allows for more than one team to be used to build the list of repositories.
• file: URL of a file in a Github repo that contains the list of repositories.

Optional query parameters:

• listinterval: Update interval for the list of monitored repos in seconds (default: 900)
• interval: Update interval for monitored repos in seconds (default: 60)
• filterusers: Only show PRs from specific users, if set in config (default: false)
• master_top: Keeps master branch failures on top of the list
• thumbs_up: Keeps PRs that have thumbs up at the top of the list
• recent: Shows the newest PRs in top of the list. The default behavior is oldest PRs on top

The Gist should contain one or more JSON files with this syntax:

[
  {
    "userName": "<username of the repo owner>",
    "repo": "<repository name>"
  }
]

You must make sure you set the language of the Gist to JSON as it will default to Text, which will not work.

Optionally, the Gist can contain a JSON file named users, to list users the team cares about. Fourth Wall can then display PRs across your tracked apps opened by these users, if the filterusers param is set. Syntax:

[
  "username0",
  "username1"
]

Optionally, entries may also contain "important": true to indicate that a repository is important. This has an effect only when the filterusers param is set: PRs on important repositories will always be displayed, even when they weren't opened by one of the listed users.

If the Gist contains a file with the language set to CSS, it will be injected into a <style> block in the document head, so you can override the default styling without having to fork this repo.

Examples:

• A simple list of repos for the Performance Platform team
• A list of repos and custom CSS for the Mainstream team
• A list of repos, custom CSS and users for the Core team

Support for other githubs

If you use github enterprise you must add the baseUrl to each repo object and add a token for that hostname. The url parameter for the other hostname should be of the form <hostname>_token.

An example enterprise repository.

[
  {
    "baseUrl": "https://myhost.com/api/v3/repos",
    "userName": "<username of the repo owner>",
    "repo": "<repository name>"
  }
]

To load repositories from a team on an enterprise instance you must prefix the hostname to the team url parameter as with the token <hostname>_team (or <hostname>_team[] for multiple teams).