Have issue and PR templates redirect to Mbed TLS #392
No reviewers
Labels
No labels
api-spec
bug
CLA requested
CLA valid
compliance
DO NOT MERGE
duplicate
enhancement
feature branch
good first issue
HEADER FORMATTING ISSUE
help wanted
Information
invalid
Jira status: AWAITING REVIEW
Jira status: CLOSED
Jira status: DONE
Jira status: IN PROGRESS
Jira status: IN REVIEW
Jira status: OPEN
Jira status: REOPENED
Jira status: RESOLVED
mirrored
mirror internally
needs: backports
needs: ci
needs: design review
needs: preceding PR
needs: review
needs: work
notabug
open for community contribution
Product Backlog
question
ready for merge
security
stale
type: bug
type: enhancement
type: question
web pages
wontfix
writing
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-ARMmbed/mbed-crypto!392
Loading…
Reference in a new issue
No description provided.
Delete branch "no-new-issue-or-pr"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is a follow-up to https://github.com/ARMmbed/mbedtls/pull/3085
We don't really want to disable issues and PR completely for this repo (for now), as this would make the existing ones invisible, and there are issues we want to track and PRs that are on their way to getting merged, and I don't think github offers and middle ground of keeping the existing ones but forbidding new ones.
So the second best thing is what this PR does: discourage people to create new issues and PRs here, and encourage them to open them in the mbedtls repo instead.
"Arm Mbed / mbedtls" instead of just "mbedtls" ?
@ -0,0 +1,10 @@We are no longer accepting new pull requests in this repositorytypo, "requrests" instead of requests
@ -0,0 +4,4 @@Mbed Crypto is now maintained as part of Mbed TLS, seehttps://github.com/ARMmbed/mbedtls/issues/3064Please open your pull request in the mbedtls repository:ditto for "mbedtls"
@ -0,0 +7,4 @@Please open your pull request in the mbedtls repository:https://github.com/ARMmbed/mbedtls/pullsThanks for your interest in Mbed Crypto!What about to add that in issue_template.md" as well?
We don't need to worry about trademark compliance in technical docs. Also, we don't want to mention Arm seeing as we want this to be open governance now. So either "mbedtls" or "Mbed TLS" is fine I think.
@ -0,0 +1,10 @@We are no longer accepting new pull requests in this repositoryAw. Thanks for catching.
I think since there is a link below it's OK to use the short name of the repo (without the organisation prefix) in the sentence.
@ -0,0 +7,4 @@Please open your pull request in the mbedtls repository:https://github.com/ARMmbed/mbedtls/pullsThanks for your interest in Mbed Crypto!I think it's there too, but for some reason the diff hides it at the end. (I'll never understand why we can't seem to come up with diff tools that generate more sensible diffs.)
ok fine by me
@ -0,0 +7,4 @@Please open your pull request in the mbedtls repository:https://github.com/ARMmbed/mbedtls/pullsThanks for your interest in Mbed Crypto!Yes I missed it, I can see it now. Sorry for the noise.
This has two approvals and we don't need to wait for the CI to complete as it's only touching files in the
.githubdirectory.