Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test issue2 #164

Closed
hm23 opened this issue Mar 18, 2024 · 2 comments
Closed

Test issue2 #164

hm23 opened this issue Mar 18, 2024 · 2 comments

Comments

@hm23
Copy link
Contributor

hm23 commented Mar 18, 2024

No description provided.

@github-actions github-actions bot added the new label Mar 18, 2024
@hm23 hm23 removed the new label Mar 18, 2024
@hm23 hm23 closed this as completed Apr 12, 2024
@daogrady
Copy link

daogrady commented Dec 17, 2024

@hm23 I just stumbled upon your workflow to automagically label new issues and wanted to point out GH's issue templates, which allow you to define different classes of issues and to give each class default labels: https://github.com/cap-js/cds-typer/blob/main/.github/ISSUE_TEMPLATE/bug_report.yaml 🙂

@hm23
Copy link
Contributor Author

hm23 commented Dec 17, 2024

@daogrady, thanks for suggesting - would be a good alternative indeed. We (node runtime team) anyhow have to clarify how we organise and monitor the various issue channels. In this context we will probably also revisit how we use labels and how this can be automated...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants