Repository navigation
Conversation
A pull request from a branch in this repository ran the test job for the commit its branch push had already tested, 18 times from 2026-09-16 to 2026-10-15. The test job now runs for pushes and for pull requests from forks, like the Docker job. The test job compiled every dependency twice without a cache: in dev for "Install dependencies" (43 s) and again in test (42 s) in https://github.com/hexpm/bob/actions/runs/38720616242/job/116373970304. It now runs in the test environment only and caches deps and _build, written only from main, as with the Docker build. bob's production database is on Postgres 18, so the service container is too. Actions are pinned to commit SHAs, the token is read-only unless a job asks for more (the repository default is write), checkouts don't keep credentials, and CodeQL and zizmor check the workflows as in hexpm. Jobs have timeouts instead of GitHub's 360-minute default. The Docker build compiles dependencies across OS processes, installs esbuild and tailwind in a cached layer instead of downloading them in assets.deploy on every build, and removes the apt lists from the image. The Docker job doesn't check out the repository: build-push-action builds from the commit's Git URL.
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A pull request from a branch in this repository ran the test job for the commit its branch push had already tested, 18 times from 2026-09-16 to 2026-10-15. The test job now runs for pushes and for pull requests from forks, like the Docker job.
The test job compiled every dependency twice without a cache: in dev for "Install dependencies" (43 s) and again in test (42 s) in https://github.com/hexpm/bob/actions/runs/38720616242/job/116373970304. It now runs in the test environment only and caches deps and _build, written only from main, as with the Docker build.
bob's production database is on Postgres 18, so the service container is too.
Actions are pinned to commit SHAs, the token is read-only unless a job asks for more (the repository default is write), checkouts don't keep credentials, and CodeQL and zizmor check the workflows as in hexpm. Jobs have timeouts instead of GitHub's 360-minute default.
The Docker build compiles dependencies across OS processes, installs esbuild and tailwind in a cached layer instead of downloading them in assets.deploy on every build, and removes the apt lists from the image. The Docker job doesn't check out the repository: build-push-action builds from the commit's Git URL.