GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - NethServer/dev: NethServer issue tracker

BranchesTags
Open more actions menu

Latest commit

 

History

134 Commits
134 Commits

Folders and files

NameName
Last commit message
Last commit date
.github
.github
 
 
developer-manual
developer-manual
 
 
handbook
handbook
 
 
scripts
scripts
 
 
CONTRIBUTING.md
CONTRIBUTING.md
 
 
README.md
README.md
 
 

Repository files navigation

NethServer development

Thank you for contributing to the NethServer project!

This GitHub repository serves on the NethServer project as official issue-tracker. Before opening a new issue here, we suggest to discuss it on community.nethserver.org.

You are welcome!

Further references:

  • Developer handbook
  • NethServer Documentation

NethServer 7 (EOL)

  • issues
  • ISO releases

NethServer 6 (EOL)

  • ns6 issue tracker archive

Label Management and Issue Status

When labels are added or removed from an issue, the issue's status in the projects is automatically updated:

  • Adding labels:

    • Adding the testing label sets the issue status to Testing.
    • Adding the verified label sets the issue status to Verified.
    • Adding one of these labels automatically removes the other if it exists.
  • Removing labels:

    • Removing the testing or verified label sets the issue status to In Progress.

This behavior is managed by a GitHub Actions workflow that runs the update_issue_status.sh script. If an issue belongs to multiple projects, all projects are updated.

Configuring the Personal Access Token (PAT)

To allow the workflow to update issue statuses in organization-level projects, an additional Personal Access Token (PAT) with the following minimum permissions is required:

  • project: full access to projects.
  • public_repo: full access to public repositories.
  • repo: full access to private repositories (only required for private repositories).

To set up the PAT correctly:

  1. Create a new PAT from your GitHub account settings, selecting the permissions listed above.
  2. Add the PAT as a secret in the repository or organization, using the name PROJECT_STATUS_BOT_TOKEN.

About

NethServer issue tracker

github.com/NethServer/dev/issues

Resources

Readme

Contributing

Contributing

Security policy

Security policy
Activity
Custom properties

Stars

69 stars

Watchers

25 watching

Forks

16 forks
Report repository

Used by

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.