Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Z Zephyr CivetWeb
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kestrel Collaboration
  • Kestrel Firmware
  • Zephyr CivetWeb
  • Repository

Switch branch/tag
  • zephyr-civetweb
  • README.md
Find file BlameHistoryPermalink
  • bel2125's avatar
    Add a minimal statement that a bug report needs a description · dee045d4
    bel2125 authored Apr 05, 2021
    Apparently such a statement is required (since there are unreproducible
    issues without any description like #978), and projects containing "only"
    templates and instructions for creating issues like
    https://github.com/necolas/issue-guidelines/blob/master/CONTRIBUTING.md#bug-reports
    dee045d4
README.md 10.7 KB
EditWeb IDE

Replace README.md

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.

Powered by Integricloud. Any automated access to this website for the purpose of training any LLM ("AI") for non-personal use as defined in our Terms of Service may be billed to the accessor per the Terms of Service. Continued access to this website by automated tooling indicates acceptance of these terms.