First-party app descriptions, the telemetry service name and instrumentation scope, and the unpacked-application temp directory. Protocol identifiers, OAuth key contexts, migration defaults and upstream license/templates are untouched.
First-party app descriptions, the telemetry service name and instrumentation scope, and the unpacked-application temp directory. Protocol identifiers, OAuth key contexts, migration defaults and upstream license/templates are untouched.
The first-party application descriptions and the telemetry service name and
instrumentation scope are shown to operators, and the unpacked-application
temp directory carried the name too.
Left alone deliberately: the OAuth key-derivation contexts (renaming them
would invalidate every sealed token and client id), the migration defaults
that read an upstream installation, links to upstream's upgrade guide, the
wire-protocol identifiers, and upstream's own license and templates.
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.
First-party app descriptions, the telemetry service name and instrumentation scope, and the unpacked-application temp directory. Protocol identifiers, OAuth key contexts, migration defaults and upstream license/templates are untouched.