You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The best route for the solution would be to submit a PR against the 3006.x branch with an update to doc/security/index.rst, which will then be included in subsequent merge-forwards.
The text was updated successfully, but these errors were encountered:
Description
Right now, the
SECURITY.md
file is representative of the latest updates around contact information and gpg public key for security reporting.Though, in the Salt docs, we have a duplicate file,
doc/security/index.rst
, that can be out-of-sync withSECURITY.md
.This
.rst
file is really a duplicate of the information inSECURITY.md
.Suggested Fix
The
doc/security/index.rst
file should just link out to theSECURITY.md
file within the repo root of themaster
branch.Type of documentation
Location or format of documentation
Published docs (coming from
doc/security/index.rst
of the latest release tag for that particular version, exceptmaster
reflects themaster
branch):latest
(currently out-of-date, because it is dependent on a new point release to update): https://docs.saltproject.io/en/latest/security/The best route for the solution would be to submit a PR against the
3006.x
branch with an update todoc/security/index.rst
, which will then be included in subsequent merge-forwards.The text was updated successfully, but these errors were encountered: