🤖 docs(AGENTS): Add AI agent context for Council Tickets tracker #571
No reviewers
Labels
No labels
category
budget
category
code-of-conduct
category
docs
category
elections
category
events
category
initiatives
category
mindshare
category
policies
category
spending-request
category
Strategy Summit
category
trademarks
Next Meeting
state
resolved
good first issue
help wanted
needs
changes
needs
reporter feedback
needs
triage
needs
vote
role
engineering
role
fca
role
foa
role
fpl
role
initiative lead
role
mindshare
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
No milestone
No project
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
council/tickets!571
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "add/agents-md"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Establish
AGENTS.mdfollowing the convention used across a few Fedora Forge repos (commops/tickets,council/flock,marketing/tickets, etc.) to provide AI coding agents with the context needed to interact with the Council's issue tracker via the Forgejo REST API.The file documents the repository structure, issue template conventions (Summary-Background-Details-Outcome format), the complete label taxonomy (org-level triage/role/scope/state labels and repo-level category labels), milestone conventions, related Council trackers, Forgejo API access patterns, terminology (OSAIPO, FPL, FCA, FOA), writing and git conventions, consent requirements for public-facing actions, and the Fedora AI-Assisted Contributions Policy.
This is part of a broader effort to bring
council/ticketsup to parity with sibling project repositories that already have instructions for AI-assisted governance workflow facilitation.I don't really have much experience with this, but LGTM I guess :)
@pbokoc I think the most important thing is that the information in the file is not outright wrong or incorrect.
Beep boop! 🤖 The robots are here. 😛 Merging! 🌊