From 162d082c72ad81d69cff567ff54abb06f31abb78 Mon Sep 17 00:00:00 2001 From: Hilmar Falkenberg Date: Wed, 14 Aug 2024 10:37:23 +0200 Subject: [PATCH] fix some lint issues --- .github/ISSUE_TEMPLATE/user_story.md | 14 ++++++------ README.md | 6 ++--- .../extensions/accessmethods/github/README.md | 8 ++----- .../extensions/accessmethods/helm/README.md | 6 ++--- .../accessmethods/localblob/README.md | 22 +++++++++---------- .../extensions/accessmethods/maven/README.md | 15 +++++++------ .../extensions/accessmethods/npm/README.md | 5 +++-- .../accessmethods/ociartifact/README.md | 7 ++---- .../accessmethods/ociblob/README.md | 7 ++---- .../accessmethods/relativeociref/README.md | 8 +++---- api/ocm/extensions/accessmethods/s3/README.md | 7 ++---- .../extensions/repositories/ocireg/README.md | 11 +++------- .../handlers/rsa-signingservice/README.md | 11 +++++----- api/utils/compression/README.md | 4 ++-- .../README.md | 4 ++-- .../03-working-with-credentials/README.md | 9 ++++---- .../docsrc/04-working-with-config/README.md | 8 ++++++- .../README.md | 4 ++-- .../06-signing-component-versions/README.md | 10 ++++++--- examples/make/README.md | 11 +++++----- migrate.md | 5 ++--- 21 files changed, 88 insertions(+), 94 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/user_story.md b/.github/ISSUE_TEMPLATE/user_story.md index 910a18d318..645631eefa 100644 --- a/.github/ISSUE_TEMPLATE/user_story.md +++ b/.github/ISSUE_TEMPLATE/user_story.md @@ -1,10 +1,8 @@ --- name: User Story about: User Story -labels: +labels: title: - Title - - --- **User Story**: The expressive title of your user story goes here @@ -15,13 +13,15 @@ As a [type of user], I want to [perform some task] so that I can [achieve some g This is a short text that just acts as an example for your user story. Please be as precise and verbose as required, so that people picking up the user story are clear about the intention and their tasks. **Epic link**: -- #410 (just mention the number of the related epic here, it will appear as clickable link later) + +- #410 (just mention the number of the related epic here, it will appear as clickable link later) **Acceptance criteria**: -- [ ] abc should have a red button in the center of the screen +- [ ] abc should have a red button in the center of the screen - [ ] on clicking the red button it should start to blink **Related issues**: -- #413 (just mention the number of the related issue here, it will appear as clickable link later) -- #414 (just mention the number of the related issue here, it will appear as clickable link later) + +- #413 (just mention the number of the related issue here, it will appear as clickable link later) +- #414 (just mention the number of the related issue here, it will appear as clickable link later) diff --git a/README.md b/README.md index e50c424715..c2c9b18e37 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,7 @@ The Open Component Model (OCM) is an open standard to describe software bills of delivery (SBOD). OCM is a technology-agnostic and machine-readable format focused on the software artifacts that must be delivered for software products. -Check out the [the main OCM project web page](https://ocm.software) to find out what OCM offers you for implementing a secure software supply chain. It is your central entry point to all kind of OCM related [docs and guides](https://ocm.software/docs/overview/about), the [OCM specification](https://ocm.software/docs/overview/specification/) and all project [github repositories](https://github.com/open-component-model). It also offers a [Getting Started](https://ocm.software/docs/getting-started/) to quickly make your hands dirty with OCM, its toolset and concepts :smiley: +Check out the [the main OCM project web page](https://ocm.software) to find out what OCM offers you for implementing a secure software supply chain. It is your central entry point to all kind of OCM related [docs and guides](https://ocm.software/docs/overview/about), the [OCM specification](https://ocm.software/docs/overview/specification/) and all project [github repositories](https://github.com/open-component-model). It also offers a [Getting Started](https://ocm.software/docs/getting-started/) to quickly make your hands dirty with OCM, its tool set and concepts :smiley: ## OCM Specifications @@ -98,7 +98,7 @@ ocm --help git-url: https://aur.archlinux.org/ocm-cli.git package-url: https://aur.archlinux.org/packages/ocm-cli -``` +```sh # if not using a helper util git clone https://aur.archlinux.org/ocm-cli.git cd ocm-cli @@ -142,7 +142,7 @@ podman build -t ocm --build-arg GO_VERSION=1.22 --build-arg ALPINE_VERSION=3.19 An example of how to use the `ocm` CLI in a Makefile can be found in [`examples/make`](https://ocm.software/ocm/blob/main/examples/make/Makefile). -More comprehensive examples can be taken from the [`components`](https://ocm.software/ocm/tree/main/components) contained in this repository. [Here](components/helmdemo/README.md) a complete component build including a multi-arch image is done and finally packaged into a CTF archive which can be tranported into an OCI repository. See the readme files for details. +More comprehensive examples can be taken from the [`components`](https://ocm.software/ocm/tree/main/components) contained in this repository. [Here](components/helmdemo/README.md) a complete component build including a multi-arch image is done and finally packaged into a CTF archive which can be transported into an OCI repository. See the readme files for details. ## Contributing diff --git a/api/ocm/extensions/accessmethods/github/README.md b/api/ocm/extensions/accessmethods/github/README.md index f0aa50c031..2499d3e669 100644 --- a/api/ocm/extensions/accessmethods/github/README.md +++ b/api/ocm/extensions/accessmethods/github/README.md @@ -1,10 +1,9 @@ # Access Method `gitHub` and `github` - Github Commit Access +## Synopsis -### Synopsis - -``` +```yaml type: gitHub/v1 ``` @@ -19,8 +18,6 @@ GitHub repository. Supported specification version is `v1` - - ### Specification Versions #### Version `v1` @@ -39,7 +36,6 @@ The type specific specification fields are: The sha/id of the git commit - ### Go Bindings The go binding can be found [here](method.go) diff --git a/api/ocm/extensions/accessmethods/helm/README.md b/api/ocm/extensions/accessmethods/helm/README.md index f7d5075365..9bc70b3bdb 100644 --- a/api/ocm/extensions/accessmethods/helm/README.md +++ b/api/ocm/extensions/accessmethods/helm/README.md @@ -1,15 +1,16 @@ # Access Method `helm` - Helm Repository Access +## Synopsis -### Synopsis -``` +```yaml type: helm/v1 ``` Provided blobs use the following media type: attribute `application/vnd.cncf.helm.chart.content.v1.tar+gzip` ### Description + This method implements the access of a Helm chart stored in a Helm chart repository. Supported specification version is `v1` @@ -36,7 +37,6 @@ The type specific specification fields are: An optional keyring used to verify the chart. - ### Go Bindings The go binding can be found [here](method.go) diff --git a/api/ocm/extensions/accessmethods/localblob/README.md b/api/ocm/extensions/accessmethods/localblob/README.md index 6c265c019a..6283370f50 100644 --- a/api/ocm/extensions/accessmethods/localblob/README.md +++ b/api/ocm/extensions/accessmethods/localblob/README.md @@ -1,9 +1,9 @@ # Access Method `localBlob` - OCM Repository Local Blob Access +## Synopsis -### Synopsis -``` +```yaml type: localBlob/v1 ``` @@ -37,7 +37,7 @@ The type specific specification fields are: - **`mediaType`** *string* - The media type of the blob used to store the resource. It may add + The media type of the blob used to store the resource. It may add format information like `+tar` or `+gzip`. - **`referenceName`** (optional) *string* @@ -50,7 +50,7 @@ The type specific specification fields are: access method [`ociArtifact`](../../../../../docs/formats/accessmethods/ociArtifact.md) is stored during some transport step as local artifact, the reference name can be set to its original repository name. An import step into an OCI based OCM - repository may then decide to make this artifact available again as + repository may then decide to make this artifact available again as regular OCI artifact. - **`globalAccess`** (optional) *access method specification* @@ -61,19 +61,18 @@ The type specific specification fields are: For example, an OCI artifact stored as local blob can be additionally stored as regular OCI artifact in an OCI registry. - + This additional external access information can be added using a second external access method specification. - ### Go Bindings The go binding can be found [here](method.go) ### Storage Mapping -Transporting component versions by value internalizes externally -referenced content (for example OCI image references). Those +Transporting component versions by value internalizes externally +referenced content (for example OCI image references). Those resources will then be stored as local blobs using the media type provided by the original blob. @@ -84,10 +83,11 @@ by registered blob handlers. #### Provided Blob Handlers The standard tool set uses the following registered blob handlers: -- *Blob handler for importing oci artifact blobs into + +- *Blob handler for importing oci artifact blobs into an OCM repository mapped to an OCI registry* - In this case the oci artifact blobs will be expanded to a regular + In this case the oci artifact blobs will be expanded to a regular OCI artifact taking the optional `referenceName`into account. -Additional blob handlers might be registered by local incarnations. \ No newline at end of file +Additional blob handlers might be registered by local incarnations. diff --git a/api/ocm/extensions/accessmethods/maven/README.md b/api/ocm/extensions/accessmethods/maven/README.md index ecb696d7a6..1f4c9484c5 100644 --- a/api/ocm/extensions/accessmethods/maven/README.md +++ b/api/ocm/extensions/accessmethods/maven/README.md @@ -1,7 +1,8 @@ # `mvn` - Maven artifacts (Java packages, jars) in a Maven (mvn) repository (e.g. mvnrepository.com) -### Synopsis -``` +## Synopsis + +```yaml type: mvn/v1 ``` @@ -9,8 +10,8 @@ Provided blobs use the following media type: `application/x-tgz` ### Description -This method implements the access of a resource hosted by a maven repository or a -complete resource set denoted by a GAV (GroupId, ArtifactId, Version). +This method implements the access of a resource hosted by a maven repository or a +complete resource set denoted by a GAV (GroupId, ArtifactId, Version). ### Specification Versions @@ -44,8 +45,8 @@ The type specific specification fields are: The optional extension of the Maven (mvn) artifact -If classifier/extension is given a dedicated resource is described, -otherwise the complete resource set described by a GAV. +If classifier/extension is given a dedicated resource is described, +otherwise the complete resource set described by a GAV. Only complete resource sets can be uploaded again to a Maven repository. #### Examples @@ -86,7 +87,7 @@ resources: access: type: mvn repository: https://repo1.maven.org/maven2 - groupId: com.sap.cloud.sdk + groupId: com.sap.cloud.sdk artifactId: sdk-modules-bom version: 5.7.0 classifier: '' diff --git a/api/ocm/extensions/accessmethods/npm/README.md b/api/ocm/extensions/accessmethods/npm/README.md index dc69976a8c..4a4e30625c 100644 --- a/api/ocm/extensions/accessmethods/npm/README.md +++ b/api/ocm/extensions/accessmethods/npm/README.md @@ -1,7 +1,8 @@ # `npm` - NPM packages in a NPM registry (e.g. npmjs.com) -### Synopsis -``` +## Synopsis + +```yaml type: npm/v1 ``` diff --git a/api/ocm/extensions/accessmethods/ociartifact/README.md b/api/ocm/extensions/accessmethods/ociartifact/README.md index 5b3b14b547..beb5828462 100644 --- a/api/ocm/extensions/accessmethods/ociartifact/README.md +++ b/api/ocm/extensions/accessmethods/ociartifact/README.md @@ -1,10 +1,9 @@ # Access Method `ociArtifact` and `ociRegistry` - OCI Artifact Access +## Synopsis -### Synopsis - -``` +```yaml type: ociArtifact/v1 ``` @@ -24,8 +23,6 @@ This method implements the access of an OCI artifact stored in an OCI registry. Supported specification version is `v1` - - ### Specification Versions #### Version `v1` diff --git a/api/ocm/extensions/accessmethods/ociblob/README.md b/api/ocm/extensions/accessmethods/ociblob/README.md index 38eed10cb0..7a14421d27 100644 --- a/api/ocm/extensions/accessmethods/ociblob/README.md +++ b/api/ocm/extensions/accessmethods/ociblob/README.md @@ -1,9 +1,9 @@ # Access Method `ociBlob` - OCI Blob Access +## Synopsis -### Synopsis -``` +```yaml type: ociBlob/v1 ``` @@ -14,8 +14,6 @@ This method implements the access of an OCI blob stored in an OCI repository. Supported specification version is `v1` - - ### Specification Versions #### Version `v1` @@ -38,7 +36,6 @@ The type specific specification fields are: The size of the blob - ### Go Bindings The go binding can be found [here](method.go) diff --git a/api/ocm/extensions/accessmethods/relativeociref/README.md b/api/ocm/extensions/accessmethods/relativeociref/README.md index a08466d4f5..4fc93f4897 100644 --- a/api/ocm/extensions/accessmethods/relativeociref/README.md +++ b/api/ocm/extensions/accessmethods/relativeociref/README.md @@ -1,10 +1,9 @@ # Access Method `relativeOciReference` - OCI Artifact Access in OCI-registry-based OCM Repository +## Synopsis -### Synopsis - -``` +```yaml type: relativeOciReference/v1 ``` @@ -30,10 +29,9 @@ the access specification. Supported specification version is `v1` - ### Specification Versions -This access method is a legacy access method formerly used to enable +This access method is a legacy access method formerly used to enable physical replication of OCI registry content together with referenced OCI artifacts. This should basically be done by a value transport of the component versions, because it diff --git a/api/ocm/extensions/accessmethods/s3/README.md b/api/ocm/extensions/accessmethods/s3/README.md index 3ecb362d09..6198e6733b 100644 --- a/api/ocm/extensions/accessmethods/s3/README.md +++ b/api/ocm/extensions/accessmethods/s3/README.md @@ -1,8 +1,8 @@ # `s3` - Blobs in a Simple Storage System (S3) +## Synopsis -### Synopsis -``` +```yaml type: s3/v1 ``` @@ -12,7 +12,6 @@ Provided blobs use the following media type: attribute `mediaType` This method implements the access of a blob stored in an S3 bucket. - ### Specification Versions Supported specification version is `v1` @@ -32,5 +31,3 @@ The type specific specification fields are: - **`key`** *string* The key of the desired blob - - diff --git a/api/ocm/extensions/repositories/ocireg/README.md b/api/ocm/extensions/repositories/ocireg/README.md index e7df056359..2315b445d2 100644 --- a/api/ocm/extensions/repositories/ocireg/README.md +++ b/api/ocm/extensions/repositories/ocireg/README.md @@ -1,10 +1,8 @@ - # Repository `OCIRegistry` and `ociRegistry` - OCI Registry based OCM Repositories +## Synopsis -### Synopsis - -``` +```yaml type: OCIRegistry/v1 ``` @@ -15,8 +13,6 @@ a dedicated OCI repository name prefix. Supported specification version is `v1`. - - ### Specification Versions #### Version `v1` @@ -34,9 +30,8 @@ The type specific specification fields are: the OCI repository prefix used for the OCM repository. - **`componentNameMapping`** (optional) *string* (deprecated) - - the mapping algorithm used to map OCM component names to OCU repository names ( `urlPath` (default) or `sha256-digest`). + the mapping algorithm used to map OCM component names to OCU repository names ( `urlPath` (default) or `sha256-digest`). ### Go Bindings diff --git a/api/tech/signing/handlers/rsa-signingservice/README.md b/api/tech/signing/handlers/rsa-signingservice/README.md index 3cfa045350..7faa330f3b 100644 --- a/api/tech/signing/handlers/rsa-signingservice/README.md +++ b/api/tech/signing/handlers/rsa-signingservice/README.md @@ -1,6 +1,6 @@ -## Signing Service +# Signing service -The type `rsa-signingservice` forwards the signing to a +The type `rsa-signingservice` forwards the signing to a signing server. The calculated digest is sent as signing request together with the used hash algorithm @@ -11,11 +11,12 @@ It must has the field `url` with the desired server address. The required credentials are taken from the credentials context using the consumer id `Signingserver.gardener.cloud`. -If uses a hostpath matcher using the identity attrutes `scheme`, `hostname`, +It uses a host path matcher using the identity attributes `scheme`, `hostname`, `port` and `pathprefix` derived from the given server URL. The expected credential properties are: -- **`clientCert`**: the client certificate used as TLS certificate and + +- **`clientCert`**: the client certificate used as TLS certificate and to authenticate the caller. - **`privateKey`**: the private key for the client certificate. -- **`caCerts`**: the CA used to validate the identity of the signining server. \ No newline at end of file +- **`caCerts`**: the CA used to validate the identity of the signing server. diff --git a/api/utils/compression/README.md b/api/utils/compression/README.md index 0c34efee42..3111ccd82d 100644 --- a/api/utils/compression/README.md +++ b/api/utils/compression/README.md @@ -1,3 +1,3 @@ This package has been taken from github.com/containers/image and -adjusted to provide an algorithn interface instead of an internal -struct. It also transparently support an None compression. \ No newline at end of file +adjusted to provide an algorithm interface instead of an internal +struct. It also transparently support a None compression. diff --git a/examples/lib/tour/docsrc/02-composing-a-component-version/README.md b/examples/lib/tour/docsrc/02-composing-a-component-version/README.md index 683d08a851..cbc9bf0b87 100644 --- a/examples/lib/tour/docsrc/02-composing-a-component-version/README.md +++ b/examples/lib/tour/docsrc/02-composing-a-component-version/README.md @@ -1,7 +1,7 @@ -{{compose-compvers}} - # Composing a Component Version +{{compose-compvers}} + This tour illustrates the basic usage of the API to create/compose component versions. diff --git a/examples/lib/tour/docsrc/03-working-with-credentials/README.md b/examples/lib/tour/docsrc/03-working-with-credentials/README.md index 0dfafdfb56..37a4775192 100644 --- a/examples/lib/tour/docsrc/03-working-with-credentials/README.md +++ b/examples/lib/tour/docsrc/03-working-with-credentials/README.md @@ -1,12 +1,14 @@ -{{credentials}} # Working with Credentials +{{credentials}} + This tour illustrates the basic handling of credentials using the OCM library. The library provides an extensible framework to bring together credential providers and credential consunmers in a technology-agnostic way. It covers four basic scenarios: + - [`basic`](01-using-credentials.go) Writing to a repository with directly specified credentials. - [`context`](02-basic-credential-management.go) Using credentials via the credential management to publish a component version. - [`read`](02-basic-credential-management.go) Read the previously created component version using the credential management. @@ -89,6 +91,7 @@ just look up the actually added version to verify the result. The coding for `describeVersion` is similar to the one shown in the [first tour]({{describe-version}}). {{using-cred-management}} + ### Using the Credential Management Passing credentials directly at the repository @@ -115,7 +118,6 @@ As usual, we start with the default OCM context. It is now used to gain access to the appropriate credential context. - ```go {{include}{../../03-working-with-credentials/02-basic-credential-management.go}{cred context}} ``` @@ -275,7 +277,7 @@ the access method as credential consumer can access the blob. ### Providing credentials via credential repositories -The OCM toolset embraces multiple storage +The OCM tool set embraces multiple storage backend technologies, for OCM metadata as well as for artifacts described by a component version. All those technologies typically have their own @@ -297,7 +299,6 @@ credentials for dedicated OCI registries. We start again by providing access to the OCM context and the connected credential context. - ```go {{include}{../../03-working-with-credentials/03-credential-repositories.go}{context}} ``` diff --git a/examples/lib/tour/docsrc/04-working-with-config/README.md b/examples/lib/tour/docsrc/04-working-with-config/README.md index 129ae46ae0..7df66e7820 100644 --- a/examples/lib/tour/docsrc/04-working-with-config/README.md +++ b/examples/lib/tour/docsrc/04-working-with-config/README.md @@ -1,12 +1,14 @@ -{{config}} # Working with Configurations +{{config}} + This tour illustrates the basic configuration management included in the OCM library. The library provides an extensible framework to bring together configuration settings and configurable objects. It covers five basic scenarios: + - [`basic`](01-basic-config-management.go) Basic configuration management illustrating the configuration of credentials. - [`generic`](02-handle-arbitrary-config.go) Handling of arbitrary configuration. - [`ocm`](03-using-ocm-config.go) Central configuration @@ -195,6 +197,7 @@ credentials, default repositories, signing keys and any other configuration specification. {{ocm-config-file}} + #### Standard Configuration File Most important are here the credentials. @@ -240,6 +243,7 @@ default initial OCM configuration file. ``` The result should look similar to (but with reordered fields): + ```yaml type: generic.config.ocm.software configurations: @@ -296,6 +300,7 @@ config object will contain the read file content, which is hopefully a valid certificate. {{tour04-arbitrary}} + ### Providing new config object types So far, we just used existing config types to configure existing objects. @@ -489,6 +494,7 @@ for some kind of ad-hoc configuration. A complete scenario is shown in the next example. {{consume-config}} + ### Preparing Objects to be Configured by the Config Management We already have our new acme.org config object type, diff --git a/examples/lib/tour/docsrc/05-transporting-component-versions/README.md b/examples/lib/tour/docsrc/05-transporting-component-versions/README.md index 69f3702c1f..2906199306 100644 --- a/examples/lib/tour/docsrc/05-transporting-component-versions/README.md +++ b/examples/lib/tour/docsrc/05-transporting-component-versions/README.md @@ -1,6 +1,7 @@ -{{transport}} # Transporting Component Versions +{{transport}} + This [tour](example.go) illustrates the basic support for transporting content from one environment into another. @@ -115,7 +116,6 @@ be migrated to local blobs. Now, we check the result of our transport action in the target repository. - ```go {{include}{../../05-transporting-component-versions/example.go}{verify-a}} {{include}{../../05-transporting-component-versions/example.go}{verify-b}} diff --git a/examples/lib/tour/docsrc/06-signing-component-versions/README.md b/examples/lib/tour/docsrc/06-signing-component-versions/README.md index ca27322f0e..0c0e0d5d4c 100644 --- a/examples/lib/tour/docsrc/06-signing-component-versions/README.md +++ b/examples/lib/tour/docsrc/06-signing-component-versions/README.md @@ -1,10 +1,12 @@ -{{signing}} # Signing Component Versions +{{signing}} + This tour illustrates the basic functionality to sign and verify signatures. It covers two basic scenarios: + - [`sign`](01-basic-signing.go) Create, Sign, Transport and Verify a component version. - [`context`](02-using-context-settings.go) Using context settings to configure signing and verification in target repo. @@ -37,6 +39,7 @@ As usual, we start with getting access to an OCM context ```go {{include}{../../06-signing-component-versions/01-basic-signing.go}{default context}} ``` + Then, we configure this context with optional ocm config defined in our config file. See [OCM config scenario in tour 04]({{ocm-config-file}}). @@ -96,6 +99,7 @@ target version. ``` {{signing-context}} + ### Using Context Settings to Configure Signing Instead of providing all signing relevant information directly with @@ -159,7 +163,7 @@ Now, we manually add the keys to our context. ``` We are prepared now and can sign any component version without specifying further options -in any repository for the signature name `acme.org`. +in any repository for the signature name `acme.org`. Therefore, we just get the component version from the prepared repository @@ -217,4 +221,4 @@ And here is a sample output containing the public and private key. ```yaml {{execute}{go}{run}{../../06-signing-component-versions}{--config}{settings.yaml}{config}{}{ocmconfig}} -``` \ No newline at end of file +``` diff --git a/examples/make/README.md b/examples/make/README.md index 17868d3add..70d2338414 100644 --- a/examples/make/README.md +++ b/examples/make/README.md @@ -2,11 +2,12 @@ This example shows how a GitOps template can be manged via OCM tooling. -It is used to deliver deploy content and +It is used to deliver deploy content and a filesystem content template for a GitOps -environment. It additionally provides some +environment. It additionally provides some tiny tooling to manage upgrades on customer side, including + - creating a new landscape based on a GitOps template - provide new versions in the customer environment - upgrade existing landscape projects (branches) based @@ -17,7 +18,7 @@ The ops part is left blank, any environment, for example Flux can be used here. The template projects is managed with *make*. -It can be used to create new versions (patch, mino, major) -and to build a component version that can later be -by the OCM toolset on the client side to import new +It can be used to create new versions (patch, minor, major) +and to build a component version that can later be +by the OCM tool set on the client side to import new versions in a customer environment. diff --git a/migrate.md b/migrate.md index 4fce985aa4..8262d6038e 100644 --- a/migrate.md +++ b/migrate.md @@ -1,6 +1,6 @@ # Migration to the new package structure -The migration to the new package sturcture was done with the Bash script +The migration to the new package structure was done with the Bash script `migrate.sh`. It can be used to repeat the migration after changes to the original structure. Options: @@ -9,7 +9,7 @@ Options: - `--module` adapt module name (to ocm.software/ocm) - `--migrator ` create a migration script usable to migrate projects using this library -# Migrating projects using this library +## Migrating projects using this library The migration was done creating a migration script `migration.mig`. It can be used to migrate packages or whole projects using this library to the new package structure and module name. @@ -19,4 +19,3 @@ It is executed by using the same migration Bash script `migrate.sh` using the op Optionally, package paths can be added as additional arguments to the command line. By default, the complete current working directory is migrated. -