apps/badges-assets
1
3
Fork 4
Code Issues 140 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Add Baker png, svg and yml. #737

Open
raydeeam wants to merge 1 commit from temp_branch into master
pull from: temp_branch
merge into: apps:master
Conversation 5 Commits 1 Files changed 12 +71222
raydeeam commented 2020-04-19 09:45:27 +00:00
First-time contributor
Copy link

This commit adds four baker badges and fixes #574

This commit adds four baker badges and fixes #574
raydeeam commented 2020-04-19 10:23:26 +00:00
Author
First-time contributor
Copy link

1 new commit added

  • add package-reviewer badge
**1 new commit added** * ``add package-reviewer badge``
raydeeam commented 2020-04-19 13:35:37 +00:00
Author
First-time contributor
Copy link

1 new commit added

  • add baker badges
**1 new commit added** * ``add baker badges``
jflory7 commented 2020-04-26 17:56:23 +00:00
Contributor
Copy link

I have always wanted a badge for this type of activity. :) Has the rule been tested, or could we have someone more savvy with fedora-messaging sign off on this? We've pushed broken badges by mistake before, so I want to be somewhat confident this works before we push it live.

I have always wanted a badge for this type of activity. :) Has the rule been tested, or could we have someone more savvy with fedora-messaging sign off on this? We've pushed broken badges by mistake before, so I want to be somewhat confident this works before we push it live.
jflory7 commented 2026-04-24 01:14:57 +00:00
Contributor
Copy link

@abompard @t0xic0der Is it possible to adapt this badge to use Matrix cookies instead of IRC karma?

@abompard @t0xic0der Is it possible to adapt this badge to use Matrix cookies instead of IRC karma?
jflory7 commented 2026-04-24 01:19:24 +00:00
Contributor
Copy link

Metadata Update from @jflory7:

  • Pull-request tagged with: C: community, D: easy, S: review, T: badge request
**Metadata Update from @jflory7**: - Pull-request tagged with: C: community, D: easy, S: review, T: badge request
This pull request is broken due to missing fork information.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin temp_branch:temp_branch
git switch temp_branch

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff temp_branch
git switch temp_branch
git rebase master
git switch master
git merge --ff-only temp_branch
git switch temp_branch
git rebase master
git switch master
git merge --no-ff temp_branch
git switch master
git merge --squash temp_branch
git switch master
git merge --ff-only temp_branch
git switch master
git merge temp_branch
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
AW: approved
artwork approved

  
AW: needed
artwork needed

  
AW: needs improvement
artwork needs improvement

  
C: community

   
C: content

   
C: development

   
C: event
  
Closed As
declined
 Closed with the reason of declined

  
Closed As
duplicate
 Closed with the reason of duplicate

  
Closed As
fixed
 Closed with the reason of fixed

  
Closed As
needs info
 Closed with the reason of needs info

  
Closed As
not yet possible
 Closed with the reason of not yet possible

  
Closed As
pushed
 Closed with the reason of pushed

  
Closed As
stale
 Closed with the reason of stale

  
C: miscellaneous

   
C: quality

   
D: easy

   
D: hard

   
D: intermediate

   
good first issue
Good for newcomers (if you want to get involved, try working on one of these!)

  
outreachy-2023
  
Priority
critical (next week)
 Priority of critical (next week)

  
Priority
minor (3-4 weeks)
 Priority of minor (3-4 weeks)

  
Priority
no deadline
 Priority of no deadline

  
Priority
normal (1-2 weeks)
 Priority of normal (1-2 weeks)

  
S: blocked
Progress blocked by another task or issue

  
S: needs rules
Waits to get rules.yml

  
S: ready to push
Ticket needs sysadmin to push a badge

  
S: request for resources
Needs artwork resources to make progress on this ticket (e.g. getting logos or other source material)

  
S: review
Tagged for follow-up review with the next triage

  
T: badge request

   
T: bug

   
T: docs
Adding or updating documentation

  
T: feature request
List the feature that should be added to tahrir.

  
Backlog Status
Needs Review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore
Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation
Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
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.

  
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
AW: approved
AW: needed
AW: needs improvement
C: community
C: content
C: development
C: event
Closed As
declined
Closed As
duplicate
Closed As
fixed
Closed As
needs info
Closed As
not yet possible
Closed As
pushed
Closed As
stale
C: miscellaneous
C: quality
D: easy
D: hard
D: intermediate
good first issue
outreachy-2023
Priority
critical (next week)
Priority
minor (3-4 weeks)
Priority
no deadline
Priority
normal (1-2 weeks)
S: blocked
S: needs rules
S: ready to push
S: request for resources
S: review
T: badge request
T: bug
T: docs
T: feature request
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
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
apps/badges-assets!737
No description provided.