releng/fedora-comps
6
1
Fork 18
Code Issues 13 Pull requests 1 Activity Actions 1

Set various repo setting here #1304

New issue
Open
opened 2026-07-09 17:52:18 +00:00 by siosm · 7 comments
siosm commented 2026-07-09 17:52:18 +00:00
Member
Copy link

We should:

  • Disable Releases, Projects, Packages, Wiki (we don't use them)
  • Disable direct pushes to this repo and enable push by PR only (via branch set rules)
  • Disable the "merge commit" and "rebase and merge commit" merge options
  • Re-enable the fast-forward only merge option
We should: - Disable Releases, Projects, Packages, Wiki (we don't use them) - Disable direct pushes to this repo and enable push by PR only (via branch set rules) - Disable the "merge commit" and "rebase and merge commit" merge options - Re-enable the fast-forward only merge option
siosm commented 2026-07-09 17:53:13 +00:00
Author
Member
Copy link
  • Allow edits by maintainers by default
  • Delete branch refs by default
  • Set "rebase and fast-forward" merge option as default
- Allow edits by maintainers by default - Delete branch refs by default - Set "rebase and fast-forward" merge option as default
siosm commented 2026-07-13 06:51:07 +00:00
Author
Member
Copy link

We should also make the validation CI check mandatory. See: #1301 (comment)

The missing packages one can require changes unrelated to the PR so we should keep it optional.

We should also make the validation CI check mandatory. See: https://forge.fedoraproject.org/releng/fedora-comps/pulls/1301#issuecomment-1060405 The missing packages one can require changes unrelated to the PR so we should keep it optional.
siosm commented 2026-07-30 14:33:24 +00:00
Author
Member
Copy link

I've filed releng/tickets#13444

I've filed https://forge.fedoraproject.org/releng/tickets/issues/13444
kevin commented 2026-07-30 18:58:58 +00:00
Owner
Copy link

Oh sheesh. I was not watching this repo for some reason. Sigh. ;(

I set all of these except:

  • Disable direct pushes to this repo and enable push by PR only (via branch set rules)
    (I think this is sometimes useful and also it's unclear how to set it?)

  • We should also make the validation CI check mandatory. See: #1301 (comment)
    (how do you do that?)

Oh sheesh. I was not watching this repo for some reason. Sigh. ;( I set all of these except: * Disable direct pushes to this repo and enable push by PR only (via branch set rules) (I think this is sometimes useful and also it's unclear how to set it?) * We should also make the validation CI check mandatory. See: #1301 (comment) (how do you do that?)
siosm commented 2026-08-07 18:23:07 +00:00
Author
Member
Copy link

You can set both via a branch rule for main.

You can set both via a branch rule for main.
siosm commented 2026-08-07 18:23:17 +00:00
Author
Member
Copy link

And thanks!

And thanks!
siosm commented 2026-08-07 18:24:19 +00:00
Author
Member
Copy link

I'll post the exact boxes to check when I get back.

I'll post the exact boxes to check when I get back.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
Closed As
Duplicate
 Closed with the reason of Duplicate

  
Closed As
Fixed
 Closed with the reason of Fixed

  
Closed As
Insufficient data
 Closed with the reason of Insufficient data

  
Closed As
Invalid
 Closed with the reason of Invalid

  
Backlog Status
Needs Review
 Needs to go through refinement

  
Backlog Status
Ready
 Ready for sprint

  
chore

   
documentation
  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
High
 This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
release-process
All the tickets that are done in order for release process.

  
Sprint Status
Blocked
 Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
 Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
 Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt
Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
 Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
 Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
 Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
 User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
Closed As
Duplicate
Closed As
Fixed
Closed As
Insufficient data
Closed As
Invalid
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
release-process
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
releng/fedora-comps#1304
No description provided.