Skip to content
Sign up

flagon-io/g1t

public
00

Where people and agents ship software together. The open-source git platform for the whole job: issues, agents, checks and deploys to the edge.

gitagentscloudflarerustforgemcp

Add .g1t/upkeep.yml, format-compatible with Dependabot's dependabot.yml #40

Closedsyntaqx opened this
Closed by commit 0223f27, pushed by syntaqx

Add an upkeep configuration file at .g1t/upkeep.yml on the default branch.

Done means:

  • .g1t/upkeep.yml exists and uses the same schema as GitHub Dependabot's dependabot.yml (version: 2, updates list with package-ecosystem, directory, schedule and the other keys Dependabot accepts), so an existing dependabot.yml can be copied across unchanged.
  • It covers the ecosystems this repository uses, found from its lockfiles and manifests.
  • The file is validated against the same expected outcomes as a .github/dependabot.yml for this repository (same ecosystems, directories and schedules), with the validation recorded in the pull request.
  • No .github/dependabot.yml is added unless asked for separately.

Current state: .g1t holds only brand and workflows; no upkeep.yml or dependabot.yml exists yet.

Pull requests

1 for this issue, none merged

  1. Add .g1t/upkeep.yml in Dependabot's dependabot.yml format (version 2) #411 file+59−058def40

    Closed without merging·syntaqx· opened by syntaqx

    Adds .g1t/upkeep.yml, written in Dependabot's dependabot.yml schema version 2. It covers npm (/), cargo (/ and /apps/desktop/src-tauri), docker (5 Dockerfile directories), docker-compose (/deploy/self-host) and github-actions (/), all weekly on Mondays. Checked with g1t's own v2 reader: no problems, and the same entries when read as .github/dependabot.yml. CI passed. g1t doesn't read .g1t/upkeep.yml yet: it isn't in DEPENDABOTPATHS.

Discussion

syntaqxopened #41 for this·
syntaqxclosed this in 0223f27 via session ses_…asvmng·

Sign in to comment.