Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: Add 11.27 release notes #411

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

WIP: Add 11.27 release notes #411

wants to merge 1 commit into from

Conversation

tas50
Copy link
Member

@tas50 tas50 commented Oct 18, 2024

Description

New week. New release

Related issue

Types of changes

  • Functional documentation bug fix (i.e., broken link or some other busted behavior)
  • New functional doc capabilities (i.e., filter search results)
  • New content
  • Revision to existing content
  • Chore (non-breaking change that does not add functionality or fix an issue)

Checklist

  • I have read the README document about contributing to this repo.
  • I have tested my changes locally and there are no issues.
  • All commits are signed.

Copy link
Contributor

Starting creation of the PREview environment...

Copy link
Contributor

PREview environment has been created at https://mondoo-pre-docs-635682756.storage.googleapis.com/docs/index.html
Please allow a few minutes for the environment to be fully deployed.

This comment has been minimized.

Copy link
Contributor

1 similar comment
Copy link
Contributor

@tas50 tas50 force-pushed the tas50/11.27 branch 2 times, most recently from c1723f0 to f30ef9f Compare October 18, 2024 22:44
Copy link
Contributor

This comment has been minimized.

Copy link
Contributor

This comment has been minimized.

Copy link
Contributor

This comment has been minimized.

Copy link
Contributor

This comment has been minimized.

Copy link
Contributor

This comment has been minimized.

Copy link
Contributor

This comment has been minimized.

Copy link
Contributor

This comment has been minimized.

Copy link
Contributor

New week. New release

Signed-off-by: Tim Smith <[email protected]>
Copy link
Contributor

@check-spelling-bot Report

🔴 Please review

See the 📂 files view, the 📜action log, or 📝 job summary for details.

Unrecognized words (3)

BAZ
DEETS
Merica

To accept these unrecognized words as correct, you could run the following commands

... in a clone of the [email protected]:mondoohq/docs.git repository
on the tas50/11.27 branch (ℹ️ how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/v0.0.22/apply.pl' |
perl - 'https://github.com/mondoohq/docs/actions/runs/11469755393/attempts/1'
Available 📚 dictionaries could cover words (expected and unrecognized) not in the 📘 dictionary

This includes both expected items (397) from .github/actions/spelling/expect.txt and unrecognized words (3)

Dictionary Entries Covers Uniquely
cspell:node/dict/node.txt 891 7 3
cspell:php/dict/php.txt 1689 5 1
cspell:java/src/java.txt 2464 4 2
cspell:python/src/python/python-lib.txt 2417 4
cspell:k8s/dict/k8s.txt 153 3 2

Consider adding them (in .github/workflows/spell-check.yaml) for uses: check-spelling/[email protected] in its with:

      with:
        extra_dictionaries:
          cspell:node/dict/node.txt
          cspell:php/dict/php.txt
          cspell:java/src/java.txt
          cspell:python/src/python/python-lib.txt
          cspell:k8s/dict/k8s.txt

To stop checking additional dictionaries, add (in .github/workflows/spell-check.yaml) for uses: check-spelling/[email protected] in its with:

check_extra_dictionaries: ''
If the flagged items are false positives

If items relate to a ...

  • binary file (or some other file you wouldn't want to check at all).

    Please add a file path to the excludes.txt file matching the containing file.

    File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

    ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

  • well-formed pattern.

    If you can write a pattern that would match it,
    try adding it to the patterns.txt file.

    Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

    Note that patterns can't match multiline strings.

Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant