Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
libc
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Issue analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
felixmoebius
libc
Commits
6c809d6b
Commit
6c809d6b
authored
5 years ago
by
gnzlbg
Browse files
Options
Downloads
Patches
Plain Diff
Add an issue template
parent
173c5be7
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
.github/issue_template.md
+22
-0
22 additions, 0 deletions
.github/issue_template.md
with
22 additions
and
0 deletions
.github/issue_template.md
0 → 100644
+
22
−
0
View file @
6c809d6b
**Help us help you.**
If you are reporting a bug, include:
*
a Minimum Working Example without any dependencies (except libc) that shows
the issue and ideally reproduces in the Rust playground
*
the target triple - libc supports many targets and many APIs
*
instructions to reproduce, logs (e.g. build logs, links to Travis-CI logs,
uploads to github gists, etc.).
If you are requesting a new API, include:
*
the target triple
*
link to the documentation of the API showing the type signatures, how to use
it, etc.
In general, just please consider that the people who can help you are all very
busy, they will be helping you in their free time, there are a lot of people in
need of help so they need to prioritize to which issues they devote their free
time, etc. So try to give most of the information upfront, be concise, show
small self-contained examples (nobody has time to create a new cargo project,
set up dependencies,...), etc. Help us help you.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment