Infrastructure/ansible
3
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions

people: Set git directories as safe #2146

Merged
ryanlerch merged 1 commit from main--fedorapeople-blanket-git-access into main 2024-07-11 17:30:17 +00:00
Conversation 5 Commits 1 Files changed 1 +10
nphilipp commented 2024-07-11 10:36:23 +00:00
Contributor
Copy link

Signed-off-by: Nils Philippsen nils@redhat.com

Signed-off-by: Nils Philippsen <nils@redhat.com>
zuul commented 2024-07-11 10:41:44 +00:00
First-time contributor
Copy link

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci
https://fedora.softwarefactory-project.io/zuul/buildset/4109472c27b04c5c9330479ed8136dd8

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci https://fedora.softwarefactory-project.io/zuul/buildset/4109472c27b04c5c9330479ed8136dd8 - [fi-ansible-lint-diff ](https://fedora.softwarefactory-project.io/zuul/build/e94a4d8674c54b33b67cea668f384491) : SUCCESS in 3m 52s - [fi-yamllint-diff ](https://fedora.softwarefactory-project.io/zuul/build/d9768015899a4287baf29f2ad67844d2) : FAILURE in 2m 26s
nphilipp commented 2024-07-11 17:23:25 +00:00
Author
Contributor
Copy link

rebased onto 129de273e9

rebased onto 129de273e9418ad12f43d382fd29b353aee6cf9f
nphilipp commented 2024-07-11 17:23:31 +00:00
Author
Contributor
Copy link

rebased onto 129de273e9

rebased onto 129de273e9418ad12f43d382fd29b353aee6cf9f
zuul commented 2024-07-11 17:28:26 +00:00
First-time contributor
Copy link

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/8d68f005cf684f608419245d4d81a263

Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/8d68f005cf684f608419245d4d81a263 - [fi-ansible-lint-diff ](https://fedora.softwarefactory-project.io/zuul/build/16154e22b54949a2a954d280e7cf9665) : SUCCESS in 4m 04s - [fi-yamllint-diff ](https://fedora.softwarefactory-project.io/zuul/build/4a47e6cac3584652a8300a9c1044cb47) : SUCCESS in 2m 27s
nphilipp commented 2024-07-11 17:30:18 +00:00
Author
Contributor
Copy link

Pull-Request has been merged by nphilipp

Pull-Request has been merged by nphilipp
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
freeze-break-request

   
post-freeze
  
blocked

Indicates the work cannot proceed. There is a dependency or an issue that is preventing the team from completing the task. This is a flag for the Scrum Master to help unblock the team.

  
Bug

The software is not behaving as expected. It could be an error, a crash, or an incorrect result. Bugs often need to be prioritized based on their severity and business impact

  
Chore

Tasks that are necessary but don't directly deliver new value to the end-user. These are internal tasks like updating a library, managing user accounts, or setting up a new service.

  
Feature

It's something that a user would be able to see or interact with, such as a new button, a new page, or an improved workflow.

  
in-progress

This label is for work that a developer is actively working on. This is usually what you'll see on the "In Progress" column of your project board.

  
points:1

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: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.

  
points:2

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:3

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:5

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:8

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.

  
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.

  
ready

indicates that an issue has been fully refined, has a story point value, and is ready to be pulled into a sprint. It has all the information needed for a developer to start working on it immediately.

  
review

This indicates that the work is complete, but it is now in a review state. This could mean a peer code review, a QA check, or a review by the Product Owner.

  
Technical Debt

work that improves the codebase without adding new features. It's work that pays down the "debt" you've accumulated, such as refactoring a messy piece of code, improving test coverage.

No labels
freeze-break-request
post-freeze
blocked
Bug
Chore
Feature
in-progress
points:1
points:13
points:2
points:3
points:5
points:8
priority:high
priority:low
priority:medium
ready
review
Technical Debt
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: Infrastructure/ansible#2146
No description provided.
Delete branch "main--fedorapeople-blanket-git-access"

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?