Go to file T
Code
.github ci: make integration step non-blocking until surfaced bugs are fixed
.shithub docs/actions: add checkout canary
bench bench: add Actions load harness
cmd worker: resolve worker count before sizing the pgx pool
deploy ops: point the uptime probe at /healthz and pin it outside the limiter
docs retro: tick the phase 3 rate-limit and metrics items
internal dbtest: serialize template setup across test processes with an advisory lock
scripts ci: match OOMScoreAdjust literally so garbage values fail the lint
seeds Add sqlc config + meta queries + generated metadb package + integration test
tests actions/runner: add setup-python shim
.air.toml Add build infra: Makefile, golangci-lint, air, GitHub Actions CI
.env.example env: document the pprof knob and fix the ignored SHITHUB_WEB_ADDR name
.gitignore deploy: add runner-only ansible playbook
.golangci.yml ci: tighten lint config (errcheck/gosec excludes, gocritic singleCaseSwitch off)
CHANGELOG.md webhook: retire TOTP fallback now that prod has zero rows on legacy key
CODE_OF_CONDUCT.md Re-baseline launch version: v1.0.0 → v0.1.0; placeholder domain → shithub.sh
CONTRIBUTING.md web/actions: render run detail and static logs (S41f)
LICENSE Add AGPLv3 LICENSE
Makefile ci: lint the shipped systemd units for memory ceilings and cron collisions
README.md Add repository packages web surface
SECURITY.md docs/runner: document DNS allowlist and secret scrub posture
THIRD_PARTY_NOTICES.md S38: THIRD_PARTY_NOTICES + go-licenses generator
docker-compose.yml swap MailHog for Mailpit (native arm64, drop-in)
go.mod Schedule dependency update configs
go.sum deps: add github.com/robfig/cron/v3 for cron expression parsing
scratch.txt add scratch file for PR pages testing
sqlc.yaml Add repository package storage accounting

Code of conduct

shithub is committed to a harassment-free experience for everyone.

We adopt the Contributor Covenant v2.1 in full. The text below is summary; the linked document is the authoritative version.

Our pledge

We pledge to make participation in our community a harassment- free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

Our standards

Examples of behavior that contributes to a positive environment:

  • Demonstrating empathy and kindness toward others.
  • Being respectful of differing opinions, viewpoints, and experiences.
  • Giving and gracefully accepting constructive feedback.
  • Accepting responsibility and apologizing to those affected by our mistakes; learning from the experience.
  • Focusing on what is best not just for ourselves but for the overall community.

Examples of unacceptable behavior:

  • The use of sexualized language or imagery, and sexual attention or advances of any kind.
  • Trolling, insulting or derogatory comments, and personal or political attacks.
  • Public or private harassment.
  • Publishing others' private information, such as a physical or email address, without their explicit permission.
  • Other conduct which could reasonably be considered inappropriate in a professional setting.

Enforcement responsibilities

Project maintainers are responsible for clarifying and enforcing standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Scope

This Code of Conduct applies within all community spaces — issue trackers, pull requests, project chat venues — and also applies when an individual is officially representing the community in public spaces.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project team at conduct@shithub.sh. All complaints will be reviewed and investigated promptly and fairly.

All project maintainers are obligated to respect the privacy and security of the reporter of any incident.

Enforcement guidelines

Project maintainers will follow the Contributor Covenant Enforcement Ladder: correction → warning → temporary ban → permanent ban, depending on severity.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 2.1.