The app has an offline fixture for its UI tests: with GCLO_UITEST_FIXTURE=1 in the environment, a workspace whose token is the fixture's fixed token is answered from a built-in organization instead of GitHub. Two things about it are looser than intended:
with the variable set, IsValidRepository answers "no" for every token, not only the fixture's, so in a real session every existing repository is treated as missing;
the variable is honoured in installed release builds, and nothing records that it was.
Scope
The fixture's git client asks the real client whether a folder is a repository.
The variable is ignored when the app runs as a Velopack-installed build.
One activity-log line when the fixture is enabled.
Threat model wording corrected.
Acceptance
The UI suite passes against the unpackaged build. Zero warnings; format clean.
## Problem
The app has an offline fixture for its UI tests: with `GCLO_UITEST_FIXTURE=1` in the environment, a workspace whose token is the fixture's fixed token is answered from a built-in organization instead of GitHub. Two things about it are looser than intended:
- with the variable set, `IsValidRepository` answers "no" for every token, not only the fixture's, so in a real session every existing repository is treated as missing;
- the variable is honoured in installed release builds, and nothing records that it was.
## Scope
- The fixture's git client asks the real client whether a folder is a repository.
- The variable is ignored when the app runs as a Velopack-installed build.
- One activity-log line when the fixture is enabled.
- Threat model wording corrected.
## Acceptance
The UI suite passes against the unpackaged build. Zero warnings; format clean.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
The app has an offline fixture for its UI tests: with
GCLO_UITEST_FIXTURE=1in the environment, a workspace whose token is the fixture's fixed token is answered from a built-in organization instead of GitHub. Two things about it are looser than intended:IsValidRepositoryanswers "no" for every token, not only the fixture's, so in a real session every existing repository is treated as missing;Scope
Acceptance
The UI suite passes against the unpackaged build. Zero warnings; format clean.