gitea/blog
44
20
Fork 31
Code Issues 10 Pull Requests 2 Actions Activity

Add blog about New Features related to labels and projects #258

Merged
lunny merged 10 commits from HesterG/blog:new-features-labels-projects into main 2023-05-11 03:33:37 +00:00
Conversation 10 Commits 10 Files Changed 14 +167
HesterG commented 2023-04-14 02:52:43 +00:00
Member
Copy Link
No description provided.
HesterG added 1 commit 2023-04-14 02:52:45 +00:00
add blog about New Features related to labels and projects
All checks were successful
continuous-integration/drone/pr Build is passing
Details
check-and-test / check-and-test (pull_request) Successful in 2m3s
Details
ef5fcdfef5
website_pr_previewer_bot commented 2023-04-14 02:54:13 +00:00
First-time contributor
Copy Link

Website preview: http://preview-gitea-org-blog-blog-258.s3-website.eu-central-1.amazonaws.com/
link to blog post: http://preview-gitea-org-blog-blog-258.s3-website.eu-central-1.amazonaws.com/2023/04/new-features-in-gitea-1.19.0-for-managing-issues-and-pull-requests/

Website preview: http://preview-gitea-org-blog-blog-258.s3-website.eu-central-1.amazonaws.com/ link to blog post: http://preview-gitea-org-blog-blog-258.s3-website.eu-central-1.amazonaws.com/2023/04/new-features-in-gitea-1.19.0-for-managing-issues-and-pull-requests/
HesterG added 1 commit 2023-04-20 03:39:58 +00:00
add a line for test
All checks were successful
check-and-test / check-and-test (pull_request) Successful in 1m19s
Details
continuous-integration/drone/pr Build is passing
Details
eecbd5755f
lunny added 2 commits 2023-04-20 04:04:05 +00:00
Remove trailling space
All checks were successful
check-and-test / check-and-test (pull_request) Successful in 1m22s
Details
continuous-integration/drone/pr Build is passing
Details
e39d024c08
HesterG added 1 commit 2023-04-24 02:33:48 +00:00
Merge branch 'main' into new-features-labels-projects
All checks were successful
check-and-test / check-and-test (pull_request) Successful in 1m20s
Details
continuous-integration/drone/pr Build is passing
Details
539cfb3d12
HesterG commented 2023-04-24 02:39:48 +00:00
Author
Member
Copy Link

Hi @techknowlogick Could you please help to review this blog, thanks!

Hi @techknowlogick Could you please help to review this blog, thanks!
techknowlogick reviewed 2023-04-26 16:20:30 +00:00
techknowlogick left a comment
Owner
Copy Link

some possible edits

some possible edits
content/post/introducing-new-features-of-labels-and-projects.md Outdated
@ -0,0 +1,165 @@
---
date: "2023-04-13T13:00:00+08:00"
author: "HesterG"
title: "New Features in Gitea 1.19.0 for Managing Issues and Pull Requests"
techknowlogick commented 2023-04-26 15:56:53 +00:00
Owner
Copy Link

Supercharge Your Issue Management Workflow: Introducing Org/User Level Projects, Scoped Labels & Advanced Label Templates

Supercharge Your Issue Management Workflow: Introducing Org/User Level Projects, Scoped Labels & Advanced Label Templates
techknowlogick marked this conversation as resolved
content/post/introducing-new-features-of-labels-and-projects.md Outdated
@ -0,0 +5,4 @@
tags: ["label", "project"]
draft: false
---
Gitea 1.19.0 has introduced new features that make it easier to manage and categorize issues and pull requests across different repositories.
techknowlogick commented 2023-04-26 15:58:41 +00:00
Owner
Copy Link
Gitea 1.19.0 brings several improvements to issue and pull request management, making it more efficient across different repositories. In this article, we'll discuss three notable new features: Organization/User Level Projects, Scoped Labels, and Advanced Label Templates. Learn how these updates can help optimize your development workflow.
``` Gitea 1.19.0 brings several improvements to issue and pull request management, making it more efficient across different repositories. In this article, we'll discuss three notable new features: Organization/User Level Projects, Scoped Labels, and Advanced Label Templates. Learn how these updates can help optimize your development workflow. ```
techknowlogick marked this conversation as resolved
content/post/introducing-new-features-of-labels-and-projects.md Outdated
@ -0,0 +11,4 @@
<!--more-->
# Organization/User Level Projects
techknowlogick commented 2023-04-26 16:00:41 +00:00
Owner
Copy Link
## Organization/User Level Projects

Organization/user level projects enable efficient issues management and pull requests across **different repositories** within the **same organization/user**. This feature allows you to conveniently track the progress of all issues and pull requests associated with a specific user or organization in one central location.

### Creating Organization/User-Level Projects

Let's use creating an organization-level project as an example:

1. Navigate to your organization page, click the "Projects" tab, and then select the "New Project" button. 

    ![new project](/demos/projects-labels/new-project.png)

2. Complete the project details, including title, description, template, and card preview. 

    > Tip: The "Basic Kanban" template is an excellent choice for project management and progress tracking, while the "Images and Text" option displays images in the card preview, which is particularly useful when an image is attached.

    ![basic kanban](/demos/projects-labels/create-project.png)

### Assigning Issues/Pull Requests to the Project

1. In the sidebar of an issue or pull request, click "Projects".
2. Choose the project to be assigned.

![set project](/demos/projects-labels/set-project.png)
``` ## Organization/User Level Projects Organization/user level projects enable efficient issues management and pull requests across **different repositories** within the **same organization/user**. This feature allows you to conveniently track the progress of all issues and pull requests associated with a specific user or organization in one central location. ### Creating Organization/User-Level Projects Let's use creating an organization-level project as an example: 1. Navigate to your organization page, click the "Projects" tab, and then select the "New Project" button. ![new project](/demos/projects-labels/new-project.png) 2. Complete the project details, including title, description, template, and card preview. > Tip: The "Basic Kanban" template is an excellent choice for project management and progress tracking, while the "Images and Text" option displays images in the card preview, which is particularly useful when an image is attached. ![basic kanban](/demos/projects-labels/create-project.png) ### Assigning Issues/Pull Requests to the Project 1. In the sidebar of an issue or pull request, click "Projects". 2. Choose the project to be assigned. ![set project](/demos/projects-labels/set-project.png) ```
techknowlogick marked this conversation as resolved
content/post/introducing-new-features-of-labels-and-projects.md
@ -0,0 +37,4 @@
![set project](/demos/projects-labels/set-project.png)
# Scoped Labels
techknowlogick commented 2023-04-26 16:05:58 +00:00
Owner
Copy Link
## Scoped Labels

Scoped labels featuring a "/" in their names function as **mutually exclusive** labels. They are ideal for **categorizing** issues and pull requests, making **filtering by labels** a breeze.

For instance, scoped labels can represent priority levels, such as "priority/high" or "priority/low," or denote the responsible team, like "team/front-end" or "team/back-end." This simplifies filtering and searching for issues and pull requests based on their categories.

### Creating Scoped Labels

1. On a repo's Issues/Pull Requests page, click the "Labels" tab and select the "New Label" button.

    ![new label](/demos/projects-labels/new-label.png)

2. Input the label name using the format "**scope/label**" and **check the "Exclusive" box** to signify that the label is mutually exclusive with other "scope/" labels.

    ![create label](/demos/projects-labels/create-label.png)

### Comparing Non-Exclusive Labels and Scoped (Exclusive) Labels

Scoped labels differ from non-exclusive labels in terms of **appearance** and **usage**:

1. Appearance: Scoped labels have a dual-colour background differentiating their scopes from names, while non-exclusive labels feature a single-coloured background.

    ![scoped label](/demos/projects-labels/scoped-labels.png)

2. Usage: Only one label under the same scope can be applied, while non-exclusive labels have no limitations.

    In the example below, labels beginning with "Priority," "Reviewed," and "Status" have scopes, and only one label can be chosen under each scope. Labels starting with "Kind" are non-exclusive, and multiple labels can be selected.

    ![add labels demo](/demos/projects-labels/labels-demo.gif)

> Tip: Once scoped labels are added, use them as categories to streamline searching for issues/pull requests based on categories/scopes.

![filter labels demo](/demos/projects-labels/labels-filter.gif)
``` ## Scoped Labels Scoped labels featuring a "/" in their names function as **mutually exclusive** labels. They are ideal for **categorizing** issues and pull requests, making **filtering by labels** a breeze. For instance, scoped labels can represent priority levels, such as "priority/high" or "priority/low," or denote the responsible team, like "team/front-end" or "team/back-end." This simplifies filtering and searching for issues and pull requests based on their categories. ### Creating Scoped Labels 1. On a repo's Issues/Pull Requests page, click the "Labels" tab and select the "New Label" button. ![new label](/demos/projects-labels/new-label.png) 2. Input the label name using the format "**scope/label**" and **check the "Exclusive" box** to signify that the label is mutually exclusive with other "scope/" labels. ![create label](/demos/projects-labels/create-label.png) ### Comparing Non-Exclusive Labels and Scoped (Exclusive) Labels Scoped labels differ from non-exclusive labels in terms of **appearance** and **usage**: 1. Appearance: Scoped labels have a dual-colour background differentiating their scopes from names, while non-exclusive labels feature a single-coloured background. ![scoped label](/demos/projects-labels/scoped-labels.png) 2. Usage: Only one label under the same scope can be applied, while non-exclusive labels have no limitations. In the example below, labels beginning with "Priority," "Reviewed," and "Status" have scopes, and only one label can be chosen under each scope. Labels starting with "Kind" are non-exclusive, and multiple labels can be selected. ![add labels demo](/demos/projects-labels/labels-demo.gif) > Tip: Once scoped labels are added, use them as categories to streamline searching for issues/pull requests based on categories/scopes. ![filter labels demo](/demos/projects-labels/labels-filter.gif) ```
techknowlogick marked this conversation as resolved
content/post/introducing-new-features-of-labels-and-projects.md Outdated
@ -0,0 +75,4 @@
![filter labels demo](/demos/projects-labels/labels-filter.gif)
# Advanced Label Templates
techknowlogick commented 2023-04-26 16:13:43 +00:00
Owner
Copy Link
## Advanced Label Templates

Advanced Label Templates are YAML files that adhere to the [YAML label format](https://github.com/go-gitea/gitea/blob/main/options/label/Advanced.yaml) and enable you to incorporate **customized sets of labels** into your Gitea instance. These labels **can be configured globally**, offering more control over your repositories' organization.

### Creating and Using Advanced Label Templates

1. In the `$GITEA_CUSTOM/options/label` directory, create a new YAML file named after the label set you wish to make, such as `documentation.yaml` for a set of documentation-related labels.

2. Define the labels using the following format:

    ```yaml
    labels:
    - name: "foo/bar"  # label name appearing in the dropdown
        exclusive: true # indicates whether to use the exclusive namespace for scoped labels. The scoped delimiter is /
        color: aabbcc   # hex color code
        description: Some label # detailed label description
    ```

    > For example, add these labels to `$GITEA_CUSTOM/options/label/documentation.yaml`:
    > ```yaml
    > labels:
    > - name: "Guide/User"
    >    color: 546e7a
    >     description: User guides or user manuals.
    > - name: "Guide/Contributor"
    >     color: 795548
    >     description: Contributor guides or documentation.
    > - name: "Guide/Best-Practice"
    >     color: 4caf50
    >     description: Documentation on best practices or recommended workflows.
    > - name: "Docs/Bug"
    >     exclusive: true
    >     color: ee0701
    >     description: An error or issue in the documentation.
    > - name: "Docs/Enhancement"
    >     exclusive: true
    >     color: 37474f
    >     description: A feature request or improvement to the documentation.
    > - name: "Docs/Formatting"
    >     exclusive: true
    >     color: 795548
    >     description: Documentation related to formatting or styling.
    > - name: "Docs/Api"
    >     exclusive: true
    >     color: 880e4f
    >     description: Documentation of an API or code library.
    > - name: "Docs/Translation"
    >     exclusive: true
    >     color: 546e7a
    >     description: Translations or requests for translation of the documentation.
    > ```

3. Implement the Label Templates

    After creating the label template, you can apply it when generating a label set for a specific repository or an organization. The new label templates will be accessible under the label set dropdown.

    For a specific repository:

    ![select label set](/demos/projects-labels/label-set.png)

    For an organization:

    ![org label set](/demos/projects-labels/org-label-set.png)

4. Use the Labels in Repositories

    The newly created labels can now be used in repositories. Choose the desired label from the label dropdown.

    ![doc labels](/demos/projects-labels/doc-labels.png)

## Streamline Issue and Pull Request Management with Scoped Labels and Organization/User Level Projects

Effectively managing issues and pull requests across multiple repositories can be daunting for organizations and individuals. However, scoped labels and organization/user-level projects provide robust tools for managing and prioritizing work.

Scoped labels enable categorizing issues and pull requests based on priority, responsible team, or other custom requirements.

These labels can be added to multiple repositories to ensure consistency across the organization. Label templates can also be utilized to customize label sets and further streamline the workflow.

Organization/user-level projects can be created to add and track issues and pull requests across different repositories. For instance, an organization with multiple repositories contributing to a single product can create projects for bug fixes, feature releases, and documentation improvements at the organizational level. Labels such as "bugs," "features," and "documentation" can then be scoped and applied to relevant issues and pull requests for better categorization and filtering.

Here is an example of an organization-level project list:

![project list](/demos/projects-labels/project-list.png)

Once issues and pull requests have been categorized, they can be easily managed within a project by simply dragging and dropping cards.
This visual representation allows for easy progress tracking and ensures that everything moves forward as planned.

![card drag demo](/demos/projects-labels/card-drag.gif)

With scoped labels and organization/user-level projects, Gitea 1.19.0 offers powerful features to enhance your issue and pull request management experience. These tools, when used effectively, can significantly improve organization and productivity across your repositories.
``` ## Advanced Label Templates Advanced Label Templates are YAML files that adhere to the [YAML label format](https://github.com/go-gitea/gitea/blob/main/options/label/Advanced.yaml) and enable you to incorporate **customized sets of labels** into your Gitea instance. These labels **can be configured globally**, offering more control over your repositories' organization. ### Creating and Using Advanced Label Templates 1. In the `$GITEA_CUSTOM/options/label` directory, create a new YAML file named after the label set you wish to make, such as `documentation.yaml` for a set of documentation-related labels. 2. Define the labels using the following format: ```yaml labels: - name: "foo/bar" # label name appearing in the dropdown exclusive: true # indicates whether to use the exclusive namespace for scoped labels. The scoped delimiter is / color: aabbcc # hex color code description: Some label # detailed label description ``` > For example, add these labels to `$GITEA_CUSTOM/options/label/documentation.yaml`: > ```yaml > labels: > - name: "Guide/User" > color: 546e7a > description: User guides or user manuals. > - name: "Guide/Contributor" > color: 795548 > description: Contributor guides or documentation. > - name: "Guide/Best-Practice" > color: 4caf50 > description: Documentation on best practices or recommended workflows. > - name: "Docs/Bug" > exclusive: true > color: ee0701 > description: An error or issue in the documentation. > - name: "Docs/Enhancement" > exclusive: true > color: 37474f > description: A feature request or improvement to the documentation. > - name: "Docs/Formatting" > exclusive: true > color: 795548 > description: Documentation related to formatting or styling. > - name: "Docs/Api" > exclusive: true > color: 880e4f > description: Documentation of an API or code library. > - name: "Docs/Translation" > exclusive: true > color: 546e7a > description: Translations or requests for translation of the documentation. > ``` 3. Implement the Label Templates After creating the label template, you can apply it when generating a label set for a specific repository or an organization. The new label templates will be accessible under the label set dropdown. For a specific repository: ![select label set](/demos/projects-labels/label-set.png) For an organization: ![org label set](/demos/projects-labels/org-label-set.png) 4. Use the Labels in Repositories The newly created labels can now be used in repositories. Choose the desired label from the label dropdown. ![doc labels](/demos/projects-labels/doc-labels.png) ## Streamline Issue and Pull Request Management with Scoped Labels and Organization/User Level Projects Effectively managing issues and pull requests across multiple repositories can be daunting for organizations and individuals. However, scoped labels and organization/user-level projects provide robust tools for managing and prioritizing work. Scoped labels enable categorizing issues and pull requests based on priority, responsible team, or other custom requirements. These labels can be added to multiple repositories to ensure consistency across the organization. Label templates can also be utilized to customize label sets and further streamline the workflow. Organization/user-level projects can be created to add and track issues and pull requests across different repositories. For instance, an organization with multiple repositories contributing to a single product can create projects for bug fixes, feature releases, and documentation improvements at the organizational level. Labels such as "bugs," "features," and "documentation" can then be scoped and applied to relevant issues and pull requests for better categorization and filtering. Here is an example of an organization-level project list: ![project list](/demos/projects-labels/project-list.png) Once issues and pull requests have been categorized, they can be easily managed within a project by simply dragging and dropping cards. This visual representation allows for easy progress tracking and ensures that everything moves forward as planned. ![card drag demo](/demos/projects-labels/card-drag.gif) With scoped labels and organization/user-level projects, Gitea 1.19.0 offers powerful features to enhance your issue and pull request management experience. These tools, when used effectively, can significantly improve organization and productivity across your repositories. ```
techknowlogick marked this conversation as resolved
content/post/introducing-new-features-of-labels-and-projects.md Outdated
@ -0,0 +162,4 @@
![card drag demo](/demos/projects-labels/card-drag.gif)
In conclusion, using scoped labels and organization/user level projects in Gitea can help streamline workflow and centralize the management of work across multiple repositories. This prioritizes and categorizes issues and pull requests more effectively, helping organizations to ensure that their projects are completed in a timely and efficient manner.
techknowlogick commented 2023-04-26 16:14:49 +00:00
Owner
Copy Link
In conclusion, implementing scoped labels and organization/user-level projects in Gitea can streamline workflows and consolidate the management of tasks across multiple repositories. This approach enables more effective prioritization and categorization of issues and pull requests, helping organizations ensure timely and efficient project completion.

We'd like to thank the [Blender Foundation](https://blender.org),  [@brechtvl](https://github.com/brechtvl), [@lunny](https://gitea.com/lunny), [@lafriks](https://gitea.com/lafriks), and many others for contributing and reviewing the functionality discussed in this blog post.
``` In conclusion, implementing scoped labels and organization/user-level projects in Gitea can streamline workflows and consolidate the management of tasks across multiple repositories. This approach enables more effective prioritization and categorization of issues and pull requests, helping organizations ensure timely and efficient project completion. We'd like to thank the [Blender Foundation](https://blender.org), [@brechtvl](https://github.com/brechtvl), [@lunny](https://gitea.com/lunny), [@lafriks](https://gitea.com/lafriks), and many others for contributing and reviewing the functionality discussed in this blog post. ```
techknowlogick marked this conversation as resolved
HesterG added 1 commit 2023-04-27 01:35:48 +00:00
update
Some checks failed
check-and-test / check-and-test (pull_request) Successful in 1m20s
Details
continuous-integration/drone/pr Build is failing
Details
1daa2861fe
HesterG commented 2023-04-27 01:36:23 +00:00
Author
Member
Copy Link

Updated to apply the suggestions above, thanks! @techknowlogick

Updated to apply the suggestions above, thanks! @techknowlogick
silverwind commented 2023-04-27 09:31:35 +00:00
Member
Copy Link

Unrelated, but some of these labels have too little contrast, may be a bug in the contrast color calculation in the UI. If this reproduces on a pristine instance, please file a bug on gitea repo.

image

Unrelated, but some of these labels have too little contrast, may be a bug in the contrast color calculation in the UI. If this reproduces on a pristine instance, please file a bug on gitea repo. ![image](/attachments/6899fa80-ed10-462f-8fc3-aeb8a9e82dbd)
image.png
20 KiB
HesterG commented 2023-04-28 01:38:27 +00:00
Author
Member
Copy Link

Unrelated, but some of these labels have too little contrast, may be a bug in the contrast color calculation in the UI. If this reproduces on a pristine instance, please file a bug on gitea repo.

image

I want to make sure that I understand this correctly, do you mean the contrast between text and background color? Just a reminder that these two labels are not scoped labels, but normal labels with a slash in the names.

Update:

I think I have found the color calculation place: 63a401ac40/modules/templates/helper.go (L524-L527)

UseLightTextColor:

63a401ac40/models/issues/label.go (L176-L187)

And for these two colors the calculation results are close to 0.35 but are greater than 0.35, so identified as dark color.

> Unrelated, but some of these labels have too little contrast, may be a bug in the contrast color calculation in the UI. If this reproduces on a pristine instance, please file a bug on gitea repo. > > ![image](/attachments/6899fa80-ed10-462f-8fc3-aeb8a9e82dbd) I want to make sure that I understand this correctly, do you mean the contrast between text and background color? Just a reminder that these two labels are not scoped labels, but normal labels with a slash in the names. Update: I think I have found the color calculation place: https://github.com/go-gitea/gitea/blob/63a401ac40ce2cc19c7d0341d11d434b568653fc/modules/templates/helper.go#L524-L527 `UseLightTextColor`: https://github.com/go-gitea/gitea/blob/63a401ac40ce2cc19c7d0341d11d434b568653fc/models/issues/label.go#L176-L187 And for these two colors the calculation results are close to 0.35 but are greater than 0.35, so identified as dark color.
techknowlogick approved these changes 2023-04-30 03:18:15 +00:00
techknowlogick added 1 commit 2023-04-30 03:18:42 +00:00
updated date
Some checks failed
check-and-test / check-and-test (pull_request) Successful in 1m19s
Details
continuous-integration/drone/pr Build is failing
Details
3fdb72efd2
techknowlogick added 1 commit 2023-04-30 03:22:02 +00:00
Merge branch 'main' into new-features-labels-projects
Some checks failed
check-and-test / check-and-test (pull_request) Successful in 1m19s
Details
continuous-integration/drone/pr Build is failing
Details
778196adc8
lunny approved these changes 2023-04-30 03:42:39 +00:00
silverwind commented 2023-04-30 18:00:39 +00:00
Member
Copy Link

Unrelated, but some of these labels have too little contrast, may be a bug in the contrast color calculation in the UI. If this reproduces on a pristine instance, please file a bug on gitea repo.

image

I want to make sure that I understand this correctly, do you mean the contrast between text and background color? Just a reminder that these two labels are not scoped labels, but normal labels with a slash in the names.

Update:

I think I have found the color calculation place: 63a401ac40/modules/templates/helper.go (L524-L527)

UseLightTextColor:

63a401ac40/models/issues/label.go (L176-L187)

And for these two colors the calculation results are close to 0.35 but are greater than 0.35, so identified as dark color.

Yes, I mean the contrast calculation seems incorrect. Will try to reproduce on try.gitea.io and if it does, file an issue.

> > Unrelated, but some of these labels have too little contrast, may be a bug in the contrast color calculation in the UI. If this reproduces on a pristine instance, please file a bug on gitea repo. > > > > ![image](/attachments/6899fa80-ed10-462f-8fc3-aeb8a9e82dbd) > > I want to make sure that I understand this correctly, do you mean the contrast between text and background color? Just a reminder that these two labels are not scoped labels, but normal labels with a slash in the names. > > Update: > > I think I have found the color calculation place: https://github.com/go-gitea/gitea/blob/63a401ac40ce2cc19c7d0341d11d434b568653fc/modules/templates/helper.go#L524-L527 > > `UseLightTextColor`: > > https://github.com/go-gitea/gitea/blob/63a401ac40ce2cc19c7d0341d11d434b568653fc/models/issues/label.go#L176-L187 > > And for these two colors the calculation results are close to 0.35 but are greater than 0.35, so identified as dark color. Yes, I mean the contrast calculation seems incorrect. Will try to reproduce on try.gitea.io and if it does, file an issue.
silverwind commented 2023-04-30 18:01:28 +00:00
Member
Copy Link

CI is failing at S3 upload

NoSuchBucket: The specified bucket does not exist
CI is failing at S3 upload ``` NoSuchBucket: The specified bucket does not exist
lunny added 1 commit 2023-05-09 01:39:26 +00:00
Merge branch 'main' into new-features-labels-projects
Some checks failed
check-and-test / check-and-test (pull_request) Successful in 1m16s
Details
continuous-integration/drone/pr Build is failing
Details
5051da9d54
lunny commented 2023-05-09 01:40:00 +00:00
Owner
Copy Link

CI is failing at S3 upload

NoSuchBucket: The specified bucket does not exist

It's for preview and it's not a blocker to merge and publish.

> CI is failing at S3 upload > > ``` > NoSuchBucket: The specified bucket does not exist It's for preview and it's not a blocker to merge and publish.
silverwind commented 2023-05-10 20:30:52 +00:00
Member
Copy Link

Should take new screenshots now that https://github.com/go-gitea/gitea/pull/24586 is in.

Should take new screenshots now that https://github.com/go-gitea/gitea/pull/24586 is in.
👍 1
HesterG added 1 commit 2023-05-11 02:39:59 +00:00
update screenshots
Some checks failed
check-and-test / check-and-test (pull_request) Successful in 1m24s
Details
continuous-integration/drone/pr Build is failing
Details
delete closed PR preview s3 / delete_preview (pull_request) Successful in 19s
Details
a7393aff66
HesterG commented 2023-05-11 02:41:03 +00:00
Author
Member
Copy Link

Should take new screenshots now that https://github.com/go-gitea/gitea/pull/24586 is in.

Updated in a7393aff66

> Should take new screenshots now that https://github.com/go-gitea/gitea/pull/24586 is in. Updated in https://gitea.com/gitea/blog/commit/a7393aff66ab1e4bcb81f0e92f2b93ca5c334149
lunny merged commit 64229c95ef into main 2023-05-11 03:33:37 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
techknowlogick
lunny
Labels
Clear labels   
in progress

   
kind/bug

   
kind/deployment

   
kind/docs

   
kind/enhancement

   
kind/feature

   
kind/lint

   
kind/proposal

   
kind/question

   
kind/security

   
kind/testing

   
kind/translation

   
kind/ui

   
lgtm/done

   
lgtm/need 1

   
lgtm/need 2

   
priority/critical

   
priority/low

   
priority/maybe

   
priority/medium

   
reviewed/duplicate

   
reviewed/invalid

   
reviewed/wontfix

   
status/blocked

   
status/needs-feedback

   
status/wip
No Label
in progress
kind/bug
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/security
kind/testing
kind/translation
kind/ui
lgtm/done
lgtm/need 1
lgtm/need 2
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
status/blocked
status/needs-feedback
status/wip
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
5 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: gitea/blog#258
No description provided.
Delete Branch "HesterG/blog:new-features-labels-projects"

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?