If you are not sure if the website you would like to visit is secure, you can verify it here. Enter the website address of the page and see parts of its content and the thumbnail images on this site. None (if any) dangerous scripts on the referenced page will be executed. Additionally, if the selected site contains subpages, you can verify it (review) in batches containing 5 pages.
favicon.ico: docs.syncthing.net/dev/issues.html - Issue Management  Syncthing do.

site address: docs.syncthing.net/dev/issues.html redirected to: docs.syncthing.net/dev/issues.html

site title: Issue Management Syncthing documentation

Our opinion (on Tuesday 17 November 2026 8:29:16 UTC):

GREEN status (no comments) - no comments

Meta tags:

Headings (most frequently used words):

issue, management, labels, milestones, assignee, locking, navigation, related, topics, quick, search, donate, support,

Text of the page (most frequently used words):
the (26), issues (17), and (16), issue (11), for (10), that (10), are (8), release (6), discussion (6), syncthing (5), version (5), this (5), don (5), bug (5), documentation (4), api (4), with (4), requests (4), related (3), management (3), github (3), been (3), duplicate (3), may (3), there (3), have (3), closed (3), from (3), not (3), released (3), milestone (3), notes (3), used (3), pull (3), problem (3), new (3), labels (3), search (2), creating (2), infrastructure (2), development (2), rest (2), working (2), introduction (2), page (2), once (2), locked (2), prevent (2), further (2), other (2), someone (2), doing (2), first (2), points (2), about (2), get (2), too (2), these (2), interface (2), clear (2), lock (2), some (2), can (2), milestones (2), require (2), set (2), bugs (2), change (2), protocol (2), label (2), merged (2), when (2), good (2), what (2), opposed (2), enhancement (2), build (2), current (2), functionality (2), configuration (2), feature (2), invalid (2), 123 (2), various (2), donate, support, quick, next, previous, overview, topics, specifications, http, utility, services, event, signing, understanding, device, ids, automatic, crash, reporting, developers, debugging, building, web, gui, usage, navigation, written, gf020590, edit, duplicates, has, identified, another, intention, move, referenced, while, just, jumping, match, might, otherwise, resurrect, contentious, bikeshedding, discussions, after, two, sides, clarified, their, point, arguing, endlessly, above, popular, attract, lots, comments, noise, annoy, people, useless, notifications, via, mail, suffers, symptom, normally, them, exceptions, though, locking, users, assigned, usually, sometimes, assigns, themself, indicate, avoid, others, mandatory, assignee, each, gets, resolved, will, added, based, present, more, information, author, how, reproduce, waiting, info, graphical, user, never, stable, introduced, fixed, such, excluded, skip, changelog, legacy, past, main, tree, rare, temporary, only, want, keep, open, visibility, but, real, somewhere, else, our, needed, validated, needs, triage, starting, contributors, contained, scope, size, desired, outcome, automatically, they, untouched, long, time, together, being, frozen, due, age, features, improvements, kind, update, dependency, file, dependencies, caused, requiring, changes, system, scripts, docker, image, missing, public, apis, config, highlight, specifically, ensure, miss, bump, minor, without, undecided, yet, know, request, whatever, reason, short, explanation, why, examples, include, discovered, error, rendered, moot, use, wontfix, things, need, tracked, types, states, also, belong, attempt, document, practice,


Text of the page (random words):
issue management syncthing documentation issue management bugs feature requests and other things we need to do are tracked as github issues issues can be of various types and in various states and also belong to milestones or not this page is an attempt to document the current practice labels issues without labels are undecided that is we don t yet know if it s a bug a configuration issue a feature request or what issues that are invalid for whatever reason are closed with a short explanation of why examples include duplicate of 123 discovered to be configuration error rendered moot by 123 and so on we don t use the invalid or wontfix labels api issues or pull requests that change public apis config rest used to highlight these specifically in the release notes and ensure we don t miss to bump the minor version bug a problem with current functionality as opposed to missing functionality enhancement build issues caused by or requiring changes to the build system scripts or docker image dependencies pull requests that update a dependency file documentation issues related to the documentation enhancement new features or improvements of some kind as opposed to a problem bug frozen due to age set automatically on issues when they have been closed untouched for a long time together with being locked for discussion good first issue good starting points for new contributors contained in scope and size and clear about what is the desired outcome needs triage new issues needed to be validated not our bug rare and temporary label used only when we want to keep an issue open for visibility but the real problem is somewhere else pr merged legacy label used in the past for pull requests merged to the main tree protocol issues that require a change to the protocol skip changelog set on bugs that have never been in a released stable version i e a bug introduced in v1 8 0 rc 1 and fixed in v1 8 0 rc 2 and as such excluded from the release notes for v1 8 0 ui issues related to the graphical user interface waiting for info issues that require more information from the author on how to reproduce milestones each released version gets a milestone issues that are resolved and will be released as that version get added to the milestone the release notes are based on the issues present in the milestone assignee users can be assigned to issues we don t usually do so sometimes someone assigns themself to an issue to indicate i m working on this to avoid others doing so too it s not mandatory locking we don t normally lock issues prevent further discussion on them there are some exceptions though popular issues that attract lots of me too and 1 comments these are noise and annoy people with useless notifications via mail and in the github interface once the issue is clear and it suffers from this symptom i may lock it contentious bikeshedding discussions after two sides in a discussion have clarified their points there is no point arguing endlessly about it as above this may get closed duplicates once an issue has been identified as a duplicate of another issue it may be locked to prevent further discussion there the intention is to move the discussion to the other referenced issue while someone just doing a search and jumping on the first match might otherwise resurrect discussion in the duplicate edit this page on github version v2 1 0 26 gf020590 written for v2 1 0 navigation introduction usage development introduction working on the web gui building syncthing debugging syncthing automatic crash reporting for developers understanding device ids syncthing infrastructure issue management creating a release release signing rest api event api http utility services api specifications related topics documentation overview development previous syncthing infrastructure next creating a release quick search donate support
Thumbnail images (randomly selected): * Images may be subject to copyright.GREEN status (no comments)
  • Logo
  • Donate

Verified site has: 16 subpage(s). Do you want to verify them? Verify pages:

1-5 6-10 11-15 16-16


The site also has references to the 1 subdomain(s)

  syncthing.net  Verify


The site also has 1 references to external domain(s).

 github.com  Verify


Top 50 hastags from of all verified websites.

Supplementary Information (add-on for SEO geeks)*- See more on header.verify-www.com

Header

HTTP/1.1 301 Moved Permanently
Connection close
Content-Length 162
Server GitHub.com
Content-Type text/html
Location htt????/docs.syncthing.net/dev/issues.html
X-GitHub-Request-Id DDCA:1C7B36:16CBDB:16E069:6AFC105C
x-github-edge-region fra
Accept-Ranges bytes
Age 0
Date Tue, 17 Nov 2026 08:29:16 GMT
Via 1.1 varnish
X-Served-By cache-rtm-ehrd2290033-RTM
X-Cache MISS
X-Cache-Hits 0
X-Timer S1794904156.280368,VS0,VE120
Vary Accept-Encoding
X-Fastly-Request-ID 08a1db29952e8ad08c46b64b049f713aee4e4928
HTTP/2 200
server GitHub.com
content-type text/html; charset=utf-8
last-modified Wed, 21 Oct 2026 07:53:48 GMT
access-control-allow-origin *
etag W/ 6ad86f8c-2782
expires Tue, 17 Nov 2026 08:39:16 GMT
cache-control max-age=600
content-encoding gzip
x-proxy-cache MISS
x-github-request-id 3706:2D8783:15392C:154C76:6AFC105C
x-github-edge-region fra
accept-ranges bytes
age 0
date Tue, 17 Nov 2026 08:29:16 GMT
via 1.1 varnish
x-served-by cache-rtm-ehrd2290038-RTM
x-cache MISS
x-cache-hits 0
x-timer S1794904156.429398,VS0,VE145
vary Accept-Encoding
x-fastly-request-id ba24c90f1ac7bcaba6a1c00429d44b5cbb8ca4af
content-length 3581

Meta Tags

title="Issue Management Syncthing documentation"
charset="utf-8"
name="viewport" content="width=device-width, initial-scale=1.0"
name="viewport" content="width=device-width, initial-scale=1"

Load Info

page size3581
load time (s)0.312223
redirect count1
speed download11477
server IP 185.199.111.153
* all occurrences of the string "http://" have been changed to "htt???/"