chore: sync upstream, configure hacktron, and automate deployment - #16
Merged
Conversation
Bumps the npm_and_yarn group with 1 update in the / directory: [uuid](https://github.com/uuidjs/uuid). Updates `uuid` from 8.3.2 to 14.0.0 - [Release notes](https://github.com/uuidjs/uuid/releases) - [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md) - [Commits](uuidjs/uuid@v8.3.2...v14.0.0) --- updated-dependencies: - dependency-name: uuid dependency-version: 14.0.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
* fix: apply org-level settings before loading repository configurations * fix: enhance descriptions and add new properties for security features in settings.json * fix: update description for deprecated squash-merge commit title property in settings.json * fix issue with archived repos --------- Co-authored-by: Yadhav Jayaraman <57544838+decyjphr@users.noreply.github.com>
…ot/npm_and_yarn/npm_and_yarn-e9ce4f7be9 Merging dependabot dependency bump: jest-junit ^16.0.0 → ^17.0.0. All checks passed.
…dates Bumps the npm_and_yarn group with 3 updates in the / directory: [js-yaml](https://github.com/nodeca/js-yaml), [qs](https://github.com/ljharb/qs) and [shell-quote](https://github.com/ljharb/shell-quote). Updates `js-yaml` from 4.1.1 to 4.2.0 - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](https://github.com/nodeca/js-yaml/commits) Updates `qs` from 6.15.0 to 6.15.2 - [Changelog](https://github.com/ljharb/qs/blob/main/CHANGELOG.md) - [Commits](ljharb/qs@v6.15.0...v6.15.2) Updates `shell-quote` from 1.8.3 to 1.8.4 - [Changelog](https://github.com/ljharb/shell-quote/blob/main/CHANGELOG.md) - [Commits](ljharb/shell-quote@v1.8.3...v1.8.4) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 4.2.0 dependency-type: direct:production dependency-group: npm_and_yarn - dependency-name: qs dependency-version: 6.15.2 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: shell-quote dependency-version: 1.8.4 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
…/allow-priorityclassname-in-helm-chart feat(helm): add priorityClassName support
Team entries are filtered by the same Diffable include/exclude logic that collaborators use, but unlike collaborators those keys were never part of the TeamSettings schema or documented, so editors and linters can't validate them. Mirror the CollaboratorSettings allOf pattern to declare include and exclude on TeamSettings, document both in the teams guide with examples, add a sample, and cover the filter path with unit tests. No runtime changes.
…ty-projects/dependabot/npm_and_yarn/npm_and_yarn-dc71bf58a9 build(deps): bump the npm_and_yarn group across 1 directory with 3 updates
…coder/team-include-exclude fix: Add the missing include/exclude repo filters to team settings schema
…nc-upstream-add-hacktron
zeyu2001
marked this pull request as ready for review
August 8, 2026 09:15
zeyu2001
changed the title
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.
Summary
github-community-projects/safe-settings:main-enterprisethroughabcf581into the HacktronAI fork without rewriting HacktronAI history.github/repos/hacktron.ymlfor the privatehacktronrepositorymainandstagingprotections explicitlyEvidence
maincurrently requires one approval, stale-review dismissal, code-owner review, last-push approval, core-team bypass/push restriction, admin enforcement, and permits force pushesstagingcurrently requires one approval without the additionalmainrestrictionsSafety
SAFE_SETTINGS_DEPLOY_ENABLEDis deliberately changed fromfalsetotrueapp-envSecret and are never copied into an imageValidation
hacktron.ymlparsed successfully withjs-yamlhacktron.ymlpassedschema/dereferenced/repos.jsonnpm run test:unit: 16 suites passed, 137 tests passednpm run lint:lockfile: passednpm run lint:engines: passednpm run lint:peer: passedbash -nforscript/bootstrap-k8s-secret: passedvalues-hacktron.yaml: passedCI
Local full-suite notes
npm testcommand also runslint:es, which reports 145 source/test style findings outsidehacktron.ymlDeployment activation still required
GCP_WORKLOAD_IDENTITY_PROVIDERandGCP_SERVICE_ACCOUNTto theproductionenvironmentrepo:HacktronAI/safe-settings:environment:productionin the GCP Workload Identity provider./script/bootstrap-k8s-secretto create/updatedefault/app-envSAFE_SETTINGS_DEPLOY_ENABLED=trueonly after those checks passThe GitHub App is already installed organization-wide with the required events. Its current webhook points to Smee; deploying the pod with
WEBHOOK_PROXY_URLinapp-envmakes Probot consume that channel without exposing a public ingress.