Based on configuration, a single-user, no-password environment should be instantiated. This will involve looking for a known user, creating it if it does not exist, and setting up the environment as if that user is logged on.
Based on configuration, a single-user, no-password environment should be instantiated. This will involve looking for a known user, creating it if it does not exist, and setting up the environment as if that user is logged on.
danieljsummers
added this to the Alpha Release project 2024-04-04 03:01:38 +00:00
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.
Based on configuration, a single-user, no-password environment should be instantiated. This will involve looking for a known user, creating it if it does not exist, and setting up the environment as if that user is logged on.
This has been implemented; the remaining functionality will be designed to run for the "current user", which will be assumed for alpha.