Skip to content
This repository was archived by the owner on Nov 17, 2023. It is now read-only.

Conversation

@marcoabreu
Copy link
Contributor

Add issue template for documentation and website since we have an increasing number of issues which are not directly related with MXNet itself but rather our documentation or website.

@mxnet-bot
Copy link

Hey @marcoabreu , Thanks for submitting the PR
All tests are already queued to run once. If tests fail, you can trigger one or more tests again with the following commands:

  • To trigger all jobs: @mxnet-bot run ci [all]
  • To trigger specific jobs: @mxnet-bot run ci [job1, job2]

CI supported jobs: [centos-cpu, website, windows-cpu, sanity, unix-cpu, miscellaneous, windows-gpu, unix-gpu, edge, centos-gpu, clang]


Note:
Only following 3 categories can trigger CI :PR Author, MXNet Committer, Jenkins Admin.
All CI tests must pass before the PR can be merged.

@marcoabreu marcoabreu changed the title Add issue template for website and documentation [COMMUNITY] Add issue template for website and documentation Sep 6, 2020
@marcoabreu marcoabreu added the pr-awaiting-review PR is waiting for code review label Sep 6, 2020
Comment on lines +10 to +16
## Current state
Link: (Insert link to location where faulty documentation is located)

(Describe what you are currently seeing in the faulty state or insert a screenshot)

## Expected state
(Describe what you'd rather expect)
Copy link
Member

Choose a reason for hiding this comment

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

the information here is insufficient to resolve issues, as essential information such as browser, systems, active plugins are missing. maybe start with bug template and adjust as needed?

Comment on lines +2 to +5
name: Documentation & Website
about: Issues regarding documentation and website
title: '[DOC/WEBSITE] '
labels: Doc, Website, needs triage
Copy link
Member

Choose a reason for hiding this comment

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

these two issues are related but not the same. maybe either split into two or pick one? otherwise the labels for doc and website will have decreased SNR

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

pr-awaiting-review PR is waiting for code review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants