Skip to content

Conversation

@da2ce7
Copy link
Contributor

@da2ce7 da2ce7 commented Oct 12, 2023

No description provided.

@da2ce7 da2ce7 force-pushed the 20231012_workflow_work branch from 4080f78 to 6f9bd73 Compare October 12, 2023 10:21
@da2ce7 da2ce7 force-pushed the 20231012_workflow_work branch from 6f9bd73 to 66679c7 Compare October 12, 2023 10:26
@da2ce7 da2ce7 changed the title Workfow Work ci: codeowners and sync labels Oct 12, 2023
@da2ce7
Copy link
Contributor Author

da2ce7 commented Oct 12, 2023

ACK 66679c7

@da2ce7 da2ce7 merged commit d2f7233 into torrust:develop Oct 12, 2023
@josecelano
Copy link
Member

Hi @da2ce7, what's the purpose of the https://github.com/torrust/torrust-index-gui/blob/develop/.github/labels.json file? Just to keep the history of labels?

@da2ce7
Copy link
Contributor Author

da2ce7 commented Oct 16, 2023

@josecelano Hello Jose.

The labels.json file defines the labels. When it is updated, the labels for the project are (should test this) automatically update via the labels.yaml workflow.

@josecelano
Copy link
Member

@josecelano Hello Jose.

The labels.json file defines the labels. When it is updated, the labels for the project are (should test this) automatically update via the labels.yaml workflow.

Yes, I understand, but why do you want to update the labels from the code? Is it because you can easily apply the same labels to other repos just by overwriting the labels.json?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants