Unify spelling to artifact and prevent regression to artefact - #150
Merged
Skarlso merged 1 commit intoAug 27, 2026
Merged
Conversation
Signed-off-by: Johannes Neisener <johannes@neisener.de> On-behalf-of: @SAP <johannes.neisener@sap.com>
jneisener
force-pushed
the
chore/unify_spelling
branch
from
August 26, 2026 16:28
665a1d6 to
7d02571
Compare
matthiasbruns
approved these changes
Aug 27, 2026
Skarlso
approved these changes
Aug 27, 2026
This was referenced Aug 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it
#146 introduced a regression in the uniform naming of
artifact.Looking at #39 and #40 this was an issue previously and
artifactwon. Presently the conventions document, whose purpose is toensure uniformityuses two different spellings.Which issue(s) this PR is related to