Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Usability] Wording rsp. inconcise reference

Open Beginner friendly
  • Is something wrong?
#3,191 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@Ph4t3 is already working on this.

Since Oct 20, 2026.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
go
Domain
content

Research direction

Find the danger-zone settings page and read the description for the switch that affects group visibility. Rewrite it to identify which group is affected and explain why changing the setting is considered dangerous; remove the redundant sentence about creating public and private assets. Done when the description is clear about the scope and risk.

Written by the indexing model from the issue text.

Description

component/devguard-web

Issue description

On https://devguard.opencode.de/%40opencode/projects/digital/settings/danger-zone the description has no practical content, because "group" seems to mean something else that a "group" in Gitlab lingo: Consequently this description is rather misleading. Specifically here, the group "evb-it" and its sub-group "EVB-IT digital" (displayed at the top of the webpage) are both public, already! There is no other "group" visible ore mentioned anywhere, hence one must come to the conclusion that these groups are becoming publicly visible, when flipping this switch.

Side note

The second sentence of the description "It allows creating public and private assets." is superfluous, because it is obvious that such a switch allows for toggling between "private" and "public". But what the rather generic word "asset" is supposed to address in this context is incomprehensible.

Suggested solution

Phrase this description anew, so it clearly denotes what kind of "group" is referred to here, and which specific "group" is going to be affected. Furthermore, a hint why this is considered dangerous would be helpful to fully comprehend the risks.

Screenshot

Image
Dominant language
Go
Stars
195
Forks
47
Avg merge
2d 19h
Merged PRs (30d)
31

Getting set up

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.

More from l3montree-dev/devguard

All issues in l3montree-dev/devguard

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.