Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/Ultimaker/Cura.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/.github
AgeCommit message (Collapse)Author
2020-10-26Clarify what a project file isGhostkeeper
Also update the name of the menu entry for 4.7+.
2020-08-28Rename workflow file to CIJaime van Kessel
2020-08-14Split up build & testJaime van Kessel
This should make the output a bit more segmented (and thus, more readable)
2020-06-19Add the no response configJaime van Kessel
2020-01-16Fix branch checkout for PRs with GitHub workflowLipu Fei
2019-12-18Fix cicd.yamlLipu Fei
2019-12-18Only run CI for master, WIP, and release branches on pushLipu Fei
2019-12-17WIP: Fix GH Actions for Uranium fetchingLipu Fei
2019-12-17WIP: Fix fetching UraniumLipu Fei
2019-12-17WIP: Fix fetching UraniumLipu Fei
2019-12-17WIP: Fix fetching UraniumLipu Fei
2019-12-17Correct GH Actions steps nameLipu Fei
2019-12-11Add GitHub ActionsLipu Fei
2019-12-09Make template a bit less intimidating and restore brackets againGhostkeeper
I think the 'why' of things is not always relevant and makes people prevent reading all of it. Keep it brief! And with all of this information that people tend to just leave there it's hard to find the actual changes that people made to the template. That's also why the brackets are important, so that it's easy to see that people didn't erase the original template text. We used to have HTML comment codes there but then people put the actual bug report inside the comments as well and nothing showed up, so this is somewhat of a middle ground that everyone understands, programmers and non-programmers.
2019-12-06Remove some mid-sentence newlines from issue templatesNino van Hooff
Newlines are tragically not ignored by Github when rendering issue\ templates, it seems
2019-12-06Break down the issue template header into sections.Nino van Hooff
I fear people might simply ignore the header, which is surrounded by comment tags. Having headings for all important pieces of information might make them stand out more.
2019-10-25Improve issue templatesGhostkeeper
Two major changes here: 1. No longer include the instructions in comments. Quite often the filled in template was also in comments then because people don't know the HTML formatting. Also if the template is not completely filled in now, public shaming ensues. 2. The reproduce steps for bugs now suggest a numbered list of steps. Hopefully this will improve the bug reports we get with better reproduction steps.
2019-06-24Update issue templatesJaime van Kessel
Added a bit more clarification to the issue template.
2019-06-17Add reproduction steps to the bug report templateGhostkeeper
It's like the most important part of a bug report, in my opinion.
2019-06-03Minor fix to the FR templateJaime van Kessel
2019-05-31Update issue templatesJaime van Kessel
2019-05-31Update issue templatesJaime van Kessel
2018-04-26Simplify issue templateGhostkeeper
We don't usually need to know what specific Qt version or graphics driver the user has, and it's a great hassle for the user to figure this out, especially when they aren't technical and just installed an official release. I hope that this leads more bug reporters to actually fill in the template.
2018-04-23Update ISSUE_TEMPLATE.mdIan Paschal
2018-03-06Update ISSUE_TEMPLATE.mdTim Kuipers
More focus on printer and attaching project file
2018-03-06Update ISSUE_TEMPLATE.mdTim Kuipers
Allow for uploading curaproject files in github directly
2018-02-28Update ISSUE_TEMPLATE.mdIan Paschal
2018-02-28Update ISSUE_TEMPLATE.mdIan Paschal
2017-12-21Improve issue template a bitChrisTerBeke
2017-12-18Create GitHub issue templateChrisTerBeke
Might help streamlining issue creation and handling.
    generated by cgit v1.2.3 (git 2.25.1) at 2024-07-14 13:08:56 +0300