l3montree-dev / l3montree-dev/devguard

Add option to open issues as confidential issues

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

Nobody has claimed this yet.

component/devguard-api feature-request
Dominant language
Go
Stars
161
Forks
43
Avg merge
1d 8h
Merged PRs (30d)
37

Description

As we are working with potential critical data (see also issue on code risks), created issues should have a confidential issue option that makes new issues confidential.

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

No files, tests, or entry points are identified in issue #906. Start by locating the issue-creation entry point and reviewing the related code-risks issue; determine how the confidential option should be exposed and verify that selecting it makes newly created issues confidential.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.