nextcloud / nextcloud/updater

Create a bug reporting template for Updater

Open
#548 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement
Dominant language
PHP
Stars
51
Forks
40
Avg merge
2d 19h
Merged PRs (30d)
3

Description

Requesting:

  • Does this problem impact web, command line, or both modes of the Updater?
  • updater.log contents
  • OS
  • Install method
  • Config (occ config:list system)
  • Filesystem types involved for { installation folder, data folder }
    • Are any filesystems NFS?

Possibly:

  • output of occ config:list core
  • ./occ config:list updatenotification

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the repository's existing issue-template configuration and how Updater issues are categorized. Create a bug-report template that requests the web or command-line mode, updater.log, OS, install method, occ config:list system output, and filesystem details; include the optional configuration commands where appropriate. Done means the rendered template prompts for the requested diagnostics.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.