Provide default GitHub workflows for format, test, Dependabot, CodeQL and Docker #161

Description

Provide default GitHub automation for formatting, tests, Dependabot, CodeQL and Docker. Main already contains repository-owned format/test/CodeQL workflows and Dependabot configuration. PR #401 adds native container validation and a copyable application publisher recipe, with remaining acceptance documented there.

The original issue has no body and does not say whether the requested defaults belong to this repository, generated applications, or reusable templates. Preserve that ambiguity until the destination is established; repository automation does not automatically appear in generated apps.

Steps to reproduce

1. Inspect the existing .github/workflows/format.yml, test.yml, codeql.yml and .github/dependabot.yml on main.
2. Review PR Scaffold hardened Axum application Docker recipes #401's container validation and application publisher scope.
3. Compare the application generator's output with the intended destination once that requirement is recorded.

Expected behavior

The agreed repository or application destination has appropriate default automation for all five requested areas, with documented permissions and runtime applicability.

Impact

Existing automation satisfies part of the title, but the unspecified destination prevents an accurate completion decision or a justified expansion into five new generated-app templates.

Proposed fix

First record the intended destination and missing behavior. Reuse existing automation and #401 Docker preparation, implement only verified gaps, and avoid copying framework-only deployment credentials or settings into consumer apps. Treat generated-application templates as a possible interpretation rather than an established requirement.

Done when

• The intended repository/application/template destination and supported runtimes are recorded.
• Existing formatting, tests, Dependabot and CodeQL coverage is mapped to that destination, with remaining gaps explicit.
• Applicable Docker validation/publication defaults are delivered with the acceptance boundaries from Axum: scaffold hardened production application Dockerfiles #398/Axum: validate multi-platform containers and provide an application publishing workflow #399.
• Any required new YAML/templates are validated and their permissions/credential needs documented.

Related

• CLI/developer-experience context: Complete CLI and local developer workflows #124; existing scaffolding Scaffold applications from reusable provider templates #130.
• Container packaging and automation Axum: scaffold hardened production application Dockerfiles #398/Axum: validate multi-platform containers and provide an application publishing workflow #399; related PR Scaffold hardened Axum application Docker recipes #401 is preparation, not proof of this unspecified full scope.
• Repository workflows.
• Dependabot configuration.