Skip to content

Add GH issue and pull request templates. - #20

Merged
tmacam merged 1 commit into
dapr-sandbox:mainfrom
tmacam:GHTemplates
Feb 8, 2023
Merged

tmacam merged 1 commit into
dapr-sandbox:mainfrom
tmacam:GHTemplates

Conversation

@tmacam

@tmacam tmacam commented Feb 7, 2023

Copy link
Copy Markdown
Collaborator

Add the CONTRIBUTING and GitHub issue templates to the repo, adapted from those in dapr/java-sdk and dapr-sandbox/components-dotnet-sdk.

Add the CONTRIBUTING and GitHub issue templates to the repo, adapted
from those in dapr/java-sdk and dapr-sandbox/component-dotnet-sdk.

Signed-off-by: Tiago Alves Macambira <tmacam@burocrata.org>
@@ -0,0 +1,19 @@
---

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI: the .NET Dapr Client SDK has this template as well, but it doesn't actually show up in the list of issue types (and GH complains about an invalid name). I wasn't able to find the cause of the error, so I left it out of the .NET Dapr Pluggable Components SDK.

@tmacam tmacam Feb 7, 2023 •

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

name: Bug report
about: Report a bug in Dapr's Java Pluggable Components SDK
title: ''
labels: kind/bug

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make sure to define the labels from the issues page.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting that you mentioned that and we already have 'Bug' and other labels by default. Curious why we went for the kind prefix

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I asked @artursouza and he said that this kind/ prefix was something they picked up from other OSS projects and that this setup is being used by dapr/dapr. I renamed the labels accordingly so this merge should work just fine.

@philliphoff philliphoff left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a couple of minor comments.

@tmacam
tmacam merged commit 38dfba9 into dapr-sandbox:main Feb 8, 2023
@tmacam
tmacam deleted the GHTemplates branch February 8, 2023 01:24
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

Successfully merging this pull request may close these issues.

2 participants