Open-Source-Orchard-Core-Extensions icon indicating copy to clipboard operation
Open-Source-Orchard-Core-Extensions copied to clipboard

OCC-245: Update OC

Open sarahelsaig opened this issue 1 year ago • 5 comments

OCC-245

sarahelsaig avatar May 28 '24 09:05 sarahelsaig

This pull request has merge conflicts. Please resolve those before requesting a review.

github-actions[bot] avatar Jun 14 '24 14:06 github-actions[bot]

This pull request has merge conflicts. Please resolve those before requesting a review.

github-actions[bot] avatar Jun 17 '24 16:06 github-actions[bot]

@check-spelling-bot Report

:red_circle: Please review

See the :open_file_folder: files view, the :scroll:action log, or :memo: job summary for details.

Unrecognized words (1)

STJ

Previously acknowledged words that are now absent Bubl listheader mediatheme notlike npmrc PII Portainer prebuild taxonomyfield textlint visualstudioextension vuejs 🫥
To accept these unrecognized words as correct and remove the previously acknowledged and now absent words, you could run the following commands

... in a clone of the [email protected]:Lombiq/Open-Source-Orchard-Core-Extensions.git repository on the issue/OCC-245 branch (:information_source: how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/Lombiq/GitHub-Actions/dev/apply.pl' |
perl - 'https://github.com/Lombiq/Open-Source-Orchard-Core-Extensions/actions/runs/9613240222/attempts/1'
Available :books: dictionaries could cover words not in the :blue_book: dictionary
Dictionary Entries Covers Uniquely
cspell:typescript/dict/typescript.txt 1098 1 1

Consider adding them (in .github/workflows/build-and-test.yml) to extra_dictionaries:

          cspell:typescript/dict/typescript.txt

To stop checking additional dictionaries, add (in .github/workflows/build-and-test.yml):

check_extra_dictionaries: ''

github-actions[bot] avatar Jun 21 '24 12:06 github-actions[bot]

@check-spelling-bot Report

:red_circle: Please review

See the :open_file_folder: files view, the :scroll:action log, or :memo: job summary for details.

Unrecognized words (1)

Dmf

Previously acknowledged words that are now absent Bubl listheader mediatheme notlike npmrc PII Portainer prebuild taxonomyfield textlint visualstudioextension vuejs 🫥
To accept these unrecognized words as correct and remove the previously acknowledged and now absent words, you could run the following commands

... in a clone of the [email protected]:Lombiq/Open-Source-Orchard-Core-Extensions.git repository on the issue/OCC-245 branch (:information_source: how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/Lombiq/GitHub-Actions/dev/apply.pl' |
perl - 'https://github.com/Lombiq/Open-Source-Orchard-Core-Extensions/actions/runs/9896693335/attempts/1'
Available :books: dictionaries could cover words not in the :blue_book: dictionary
Dictionary Entries Covers Uniquely
cspell:typescript/dict/typescript.txt 1098 1 1

Consider adding them (in .github/workflows/build-and-test.yml) to extra_dictionaries:

          cspell:typescript/dict/typescript.txt

To stop checking additional dictionaries, add (in .github/workflows/build-and-test.yml):

check_extra_dictionaries: ''

github-actions[bot] avatar Jul 11 '24 18:07 github-actions[bot]

This pull request has merge conflicts. Please resolve those before requesting a review.

github-actions[bot] avatar Jul 13 '24 14:07 github-actions[bot]

This is all done, I'm only waiting for the Windows visual verification pic to generate on the server since I can't do it locally.

sarahelsaig avatar Jul 24 '24 14:07 sarahelsaig

Now please update NuGetTest.

Piedone avatar Jul 26 '24 22:07 Piedone

Now please update NuGetTest.

Why is that necessary? Do we anticipate anything different in NuGet that would justify the effort of publishing all remaining Lombiq projects to Cloudsmith as well?

sarahelsaig avatar Jul 26 '24 23:07 sarahelsaig

Not to Cloudsmith, to NuGet, as alphas as usual. Because now the NuGet build is disabled and the NuGetTest app is not updated.

But if you think that upgrading that solution to 2.0 won't be a big deal once all the packages are published, then we don't need to do it now.

Piedone avatar Jul 26 '24 23:07 Piedone