Skip to content

requirements#67

Merged
AlexanderLanin merged 27 commits into
mainfrom
requirements
Jun 13, 2025
Merged

requirements#67
AlexanderLanin merged 27 commits into
mainfrom
requirements

Conversation

@AlexanderLanin
Copy link
Copy Markdown
Member

@AlexanderLanin AlexanderLanin commented Jun 3, 2025

initial set of docs-as-code requirements

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 3, 2025

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //src:license-check

Status: ⚠️ Needs Review

Click to expand output
[License Check Output]
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
INFO: Invocation ID: 81d9b045-16ea-40fe-9cfc-5a4e547405f3
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: src
Loading: 0 packages loaded
    currently loading: src
Analyzing: target //src:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //src:license-check (1 packages loaded, 0 targets configured)

Analyzing: target //src:license-check (103 packages loaded, 10 targets configured)

Analyzing: target //src:license-check (147 packages loaded, 1774 targets configured)

Analyzing: target //src:license-check (157 packages loaded, 2666 targets configured)

Analyzing: target //src:license-check (157 packages loaded, 2682 targets configured)

Analyzing: target //src:license-check (161 packages loaded, 4815 targets configured)

INFO: Analyzed target //src:license-check (162 packages loaded, 4941 targets configured).
INFO: Found 1 target...
Target //src:license.check.license_check up-to-date:
  bazel-bin/src/license.check.license_check
  bazel-bin/src/license.check.license_check.jar
INFO: Elapsed time: 16.144s, Critical Path: 0.45s
INFO: 13 processes: 4 disk cache hit, 9 internal.
INFO: Build completed successfully, 13 total actions
INFO: Running command line: bazel-bin/src/license.check.license_check src/formatted.txt -review -project automotive.score -repo https://github.com/eclipse-score/docs-as-code -token otyhZ4eaRYK1tKLNNF-Y
[main] INFO Querying Eclipse Foundation for license data for 83 items.
[main] INFO Found 58 items.
[main] INFO Querying ClearlyDefined for license data for 25 items.
[main] ERROR Error response from ClearlyDefined 429

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 4, 2025

The created documentation from the pull request is available at: docu-html

AlexanderLanin and others added 15 commits June 11, 2025 11:20
Co-authored-by: Maximilian Sören Pollak <MaximilianSoerenPollak@users.noreply.github.com>
Co-authored-by: Alexander Lanin <Alexander.Lanin@bosch.com>
Added needpie to showcase implemeneted status
Removed some TODOs
Added notes where applicable
Changed headers to be similar to the rest
@AlexanderLanin
Copy link
Copy Markdown
Member Author

@MaximilianSoerenPollak I've just tried rebasing and squashing all of this. I ended up with 0 changes. I don't see any need to clean this PR up before final review.

@AlexanderLanin AlexanderLanin marked this pull request as ready for review June 12, 2025 20:36
@AlexanderLanin AlexanderLanin requested a review from Copilot June 12, 2025 20:37
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR introduces the initial docs-as-code requirements and landing pages by adding new product and how-to guides, updating the root and product indexes, and adjusting build and editor configurations.

  • Added product landing with “Features” and “Requirements” cards and updated toctree
  • Introduced core “Capabilities”, “How to Use”, and “How to Integrate” documentation
  • Updated Bazel and external-needs configuration, enabled Myst colon-fence, and added VSCode settings

Reviewed Changes

Copilot reviewed 25 out of 25 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
docs/product/index.rst Updated product index grid layout and toctree entries
docs/product/extensions/metamodel.md Removed outdated “Getting started” link
docs/product/capabilities.md Added new capabilities document
docs/index.rst Revised main index cards and expanded sitemap toctree
docs/how-to-use/index.rst Added “How To Use” landing page
docs/how-to-integrate/index.rst Added “How to Integrate” landing page
docs/how-to-integrate/getting_started.md Updated example link and removed extensions overview
docs/how-to-integrate/example/testing/index.rst Updated need ID in example
docs/how-to-integrate/example/index.rst Updated need ID in example
docs/conf.py Enabled myst_enable_extensions = ["colon_fence"]
docs/BUILD Added external_needs_info and targets for score_process
MODULE.bazel Added bazel_dep for score_process
.vscode/settings.json Reformatted Bazel LSP args and disabled internal type checking
Comments suppressed due to low confidence (3)

docs/product/extensions/metamodel.md:6

  • The Getting Started link was removed; consider replacing it with a pointer to the new 'How to Integrate' or 'How to Use' guide so readers can find setup instructions for this extension.
See [Getting started](../getting_started) for more information on why we use extensions.

docs/how-to-use/index.rst:12

  • The toctree references 'faq', but no docs/how-to-use/faq.rst file exists. Please verify the filename or add the missing FAQ document.
*   faq

docs/how-to-integrate/getting_started.md:129

  • The 'Available Extensions' section was removed, potentially leaving users without guidance. Ensure that extension overviews are available elsewhere or link them from a central index.
## Available Extensions

Comment thread docs/product/index.rst
Comment thread docs/product/capabilities.md Outdated
@MaximilianSoerenPollak
Copy link
Copy Markdown
Contributor

@MaximilianSoerenPollak I've just tried rebasing and squashing all of this. I ended up with 0 changes. I don't see any need to clean this PR up before final review.

I think overall the PR looks good. We have now gone over it quiet a bit.
I think anything else that we may find can be addressed in future PR's.

Copy link
Copy Markdown
Contributor

@MaximilianSoerenPollak MaximilianSoerenPollak left a comment

Choose a reason for hiding this comment

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

Just the comments, but those can be fixed / addressed in later PR's.

Glad we can finally merge this, what a saga.

Comment thread docs/product/capabilities.md Outdated
Comment thread docs/product/capabilities.md Outdated
Comment thread docs/product/capabilities.md
- Latest documentation (e.g. `main` branch)
- ✅ Keeps linked repositories and their rendered websites unaffected by incoming references
- Allows bidirectional links for integration-focused documentation
- In addition to high level versioning of repositories, supports verifying suspect links on a requirement level
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Not quiet sure what suspect links are.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Random website:

A link is 'Suspect' when the Object was modified more recently than the corresponding link attribute

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

We should add that to our documentation/glossary

- ✅ Live preview functionality for documentation authors
- ✅ Integrated linting for:
- Syntax and formatting (reST and Markdown)
- Internal and external link validity
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Internal yes (through sphinx / esbonio) ?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I think that was meant to refer to external needs. And those are checked.

Comment thread src/extensions/score_metamodel/metamodel.yaml
Co-authored-by: Maximilian Sören Pollak <maximilian.pollak@expleogroup.com>
Signed-off-by: Alexander Lanin <alex@lanin.de>
Copy link
Copy Markdown
Contributor

@MaximilianSoerenPollak MaximilianSoerenPollak left a comment

Choose a reason for hiding this comment

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

👍

@AlexanderLanin AlexanderLanin merged commit 9c7cef3 into main Jun 13, 2025
7 checks passed
@AlexanderLanin AlexanderLanin deleted the requirements branch June 13, 2025 06:25
arnoox pushed a commit to arnoox/score-docs-as-code that referenced this pull request Feb 20, 2026
Co-authored-by: Maximilian Sören Pollak <maximilian.pollak@expleogroup.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

3 participants