Update bug_report.yaml - Githubissues

Megabit / Blazorise

Blazorise is a component library built on top of Blazor with support for CSS frameworks like Bootstrap, Tailwind, Bulma, AntDesign, and Material.

https://blazorise.com/

Other

3.32k stars 535 forks source link

Update bug_report.yaml #5828

Closed tesar-tech closed 2 weeks ago

tesar-tech commented 3 weeks ago

Description

Closes #5822

Multiple bug report repositories were created, one for each provider, with a central hub available here. The automation is managed by a GitHub Action.
For each provider, the action uses Blazorise.Templates to generate fresh, up-to-date code.
It pushes the generated code to the corresponding Bug Report repository (e.g., BugReportBootstrap5). (so the provider repos are "orphaned")
Additionally, it copies the README, license, and .gitignore files to each repository.
The README provides basic instructions on how to use the template.
The action runs daily to:
- Ensure unique names for each repository (with MMdd suffix), helping us avoid duplicate .NET project names.
- Keep all repositories up-to-date by using the latest -f flag and installing the newest Blazorise.Templates version.

tesar-tech commented 2 weeks ago

I am not sure I understand the suggestion.

the repositories are generated - not in their own action, but in the BugReportTemplate action. What would be the benefit to do it in their own gh actions?
I can also add the dotnet build into the BugReportTemplate action. But I don't find it necessary - I somehow trust the Blazorise.Template will produce "buildable" repo. The right place to test this is on the Blazorise.Template side (but I understand the reality and this is really one line of code to add).

stsrki commented 2 weeks ago

Might be good to also update label action and mention that they can use new project template for reproducible.

https://github.com/Megabit/Blazorise/blob/master/.github/label-actions.yml

David-Moreira commented 2 weeks ago

I am not sure I understand the suggestion.

the repositories are generated - not in their own action, but in the BugReportTemplate action. What would be the benefit to do it in their own gh actions?

I can also add the dotnet build into the BugReportTemplate action. But I don't find it necessary - I somehow trust the Blazorise.Template will produce "buildable" repo. The right place to test this is on the Blazorise.Template side (but I understand the reality and this is really one line of code to add).

No I meant the second option. It was just a double check, no harm I guess. But you're right about the right place to making sure Blazorise.Template is working correctly is on its own repository.