Skip to content

doc: Improve godoc for Source Code Spec #1846

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

Merged
merged 1 commit into from
Mar 27, 2025

Conversation

adambkaplan
Copy link
Member

Changes

Adding clearer descriptions of the source code spec options for Build and BuildRun objects. This is particularly relevant for the OCIArtifact source type, which extracts the contents of a "scratch" container image to a local directory.

These updated godoc comments should then get synced to the docs repository and published at https://shipwright.io/docs/ref/api/build/.

/kind documentation

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

NONE

@openshift-ci openshift-ci bot added the release-note-none Label for when a PR does not need a release note label Mar 26, 2025
@pull-request-size pull-request-size bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Mar 26, 2025
@openshift-ci openshift-ci bot added the kind/documentation Categorizes issue or PR as related to documentation. label Mar 26, 2025
Adding clearer descriptions of the source code spec options for `Build`
and `BuildRun` objects. This is particularly relevant for the
`OCIArtifact` source type, which extracts the contents of a "scratch"
container image to a local directory.

These updated godoc comments should then get synced to the docs
repository and published at https://shipwright.io/docs/ref/api/build/.

Signed-off-by: Adam Kaplan <[email protected]>
Copy link
Member

@SaschaSchwarze0 SaschaSchwarze0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@SaschaSchwarze0 SaschaSchwarze0 added this to the release-v0.16.0 milestone Mar 27, 2025
Copy link
Contributor

openshift-ci bot commented Mar 27, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SaschaSchwarze0

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 27, 2025
@SaschaSchwarze0
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 27, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 9763de3 into shipwright-io:main Mar 27, 2025
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/documentation Categorizes issue or PR as related to documentation. lgtm Indicates that a PR is ready to be merged. release-note-none Label for when a PR does not need a release note size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants