chore(deps): bump actions/checkout from 4 to 6 #27
Conversation
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
) - Add stylized circular letter badges (A-M) to replace identical refresh icons - Remove letter prefixes from card titles (badge already shows letter) - Fix YAML frontmatter: quote titles with colons and fix indentation - Ensure all objective summaries are consistently italicized - Update sidebar navigation to show lettered objectives alphabetically - Add CSS styling for badge hover effects and dark mode support
…nt (#23) - Add comprehensive content covering composable business concept - Add comparison table between Composable Business and Reuse Enablement - Use MkDocs Material tip admonition for key insights section - Add ChatGPT-style table styling (no vertical borders, subtle horizontal lines) - Include package statistics (npm: 3.5M+, PyPI: 600K+ packages) - Add links to npmjs.org and pypi.org - Format all content with 70-character line wrapping - Enhance blockquote styling in CSS (for future use)
- Add comprehensive content covering reuse enablement as core architectural principle - Add 'Beyond Data: The Real Meaning of Reuse' section explaining paradigm shift - Add comparison table between Reuse Enablement and Composable Business - Include Mermaid diagram showing progression: Data → Information → Knowledge → Behaviour → Reusable Use Case → Composable Enterprise - Add practical guide on how to enable reuse (5 steps) - Include package statistics (npm: 3.5M+, PyPI: 600K+ packages) with links - Use MkDocs Material tip admonitions for key insights - Format all content with 70-character line wrapping - Update summary to reflect comprehensive nature of the page
- Add 'From DIKW to EKGF: Making Knowledge Executable' section - Explain how EKGF Method extends DIKW model with operational dimension - Include DIKW revised diagram showing path to executable knowledge - Add image asset (dikw-revised.svg) to docs/assets/ - Remove old screenshot files that are no longer needed - Fix merge conflict markers in enable-reuse.md
dependabot
bot
added
dependencies
- Remove 'work in progress' warning and polish content - Add clear introduction and summary sections - Convert bullet-heavy sections into flowing paragraphs - Improve visual hierarchy with tip boxes and better structure - Add relationship to other concepts section - Ensure all lines under 70 characters - Better connect to Enable Reuse and Composable Business objectives
Configure pymdownx.tabbed to generate anchor names from tab titles instead of generic __tabbed_1_2 identifiers, making URLs more readable and meaningful.
Enhanced all tabbed sections with better organization, clearer explanations, and improved readability. Added new sections, expanded existing content, and ensured consistent formatting throughout.
Update FAQ link from old __tabbed_1_5 format to new slugified anchor name plan-build-run for the Plan/Build/Run tab.
- Add summary block for consistency with other concept pages
- Expand Business & Management Audience tab with better structure
- Significantly enhance Data & Tech Audience tab:
- Add Persona vs. Actor vs. Role comparison
- Add Real-Time Persona Computation section explaining EKG service
layer capabilities
- Expand Ontology-Based Definition with concept vocabulary reuse
- Add Relationship to Stories section
- Add Persona Inheritance section with examples
- Expand Model tab with overview and key relationships
- Add links to related concepts throughout
- Fix typo: Pursuent -> Pursuant
- Ensure all lines under 70 characters
- Add summary block for consistency with other concept pages
- Expand Business & Management Audience tab:
- Add What Is a Story? section
- Add Story Structure section explaining Who/What/Why format
- Add tip admonition about starting simple
- Improve examples formatting
- Add Why Stories Matter section
- Significantly enhance Data & Tech Audience tab:
- Add What Is a Story in the EKG Method? section
- Add The Challenge section
- Restructure Structured Business User Stories with subsections:
Strategic Focus, Gap Analysis, Avoid Tunnel Thinking,
Separation of Concerns, Testable Specifications
- Add Continuous Testing and Functional Health section
- Add Relationship to Other Concepts section
- Remove TODO placeholders and replace with structured content
- Add links to related concepts (Persona, Use Case, Outcome, Concept)
- Ensure all lines under 70 characters
- Add summary block for consistency with other concept pages
- Add tabbed content structure (Business & Management Audience,
Data & Tech Audience)
- Fix syntax error (removed erroneous comma)
- Expand Business & Management Audience tab:
- Add What Is a Concept? section
- Add Why Concepts Matter section
- Add tip admonition about starting with business language
- Add Concept Vocabulary section
- Add Evolution and Refinement section
- Significantly enhance Data & Tech Audience tab:
- Add What Is a Concept in the EKG Method? section
- Add The Concept Lifecycle with subsections
- Add Concept Types section (Class, Property, Shape)
- Add Concepts as Linking Pins section explaining how concepts
link business and technical terms across all manifestations
(forms, code, SPARQL, databases, APIs, OWL axioms, SHACL shapes)
- Expand Relationship to Ontologies section
- Add Reuse and Inheritance section
- Add Relationship to Other Concepts section
- Add links to related concepts (Use Case, Use Case Tree, Persona,
Story, Ontology)
- Ensure all lines under 70 characters
- Add summary block for consistency with other concept pages
- Add tabbed content structure (Business & Management Audience,
Data & Tech Audience)
- Expand Business & Management Audience tab:
- Add What Is an Outcome? section
- Add Why Outcomes Matter section
- Add tip admonition about starting with outcomes
- Add Outcome Characteristics section
- Add Examples section with concrete examples
- Add Measuring Outcomes section
- Significantly enhance Data & Tech Audience tab:
- Add What Is an Outcome in the EKG Method? section
- Add Outcome Structure section
- Add Outcome Stereotypes section explaining how Goal, Objective,
Definition of Done, etc. are stereotypes of Outcome
- Add Relationship to Stories section explaining Who/What/Why
- Add Alignment with Strategy section
- Add Measuring and Tracking section
- Add Relationship to Other Concepts section
- Add links to related concepts (Use Case, Story, Persona)
- Transform single paragraph into structured, comprehensive content
- Ensure all lines under 70 characters
- Add summary block for consistency with other concept pages
- Add tabbed content structure (Business & Management Audience,
Data & Tech Audience, DPROD Ontology)
- Expand Business & Management Audience tab:
- Add The Data Economy section explaining supply (data products)
vs demand (use cases) concept
- Add What Is a Data Product? section
- Add Why Data Products Matter section
- Add tip admonition about semantic relevance
- Add When Are Data Products Used? section
- Significantly enhance Data & Tech Audience tab:
- Add What Is a Data Product in the EKG Method? section
- Add Semantic Data Products section
- Add Selection Criteria section with tip about semantic matching
- Add Lifecycle Integration section
- Add Relationship to Other Concepts section
- Add Reuse and Composition section
- Add important admonition explaining that Data Products are
Use Cases with stereotypes (data-product, upstream data-source,
downstream data-sink, etc.)
- Add new DPROD Ontology tab:
- What Is DPROD and why it exists
- DPROD principles (decentralize data ownership, harmonize schemas)
- DPROD model overview (Data Product, Ports, Distributions, Datasets)
- Relationship to EKG Method
- Key features and link to DPROD documentation
- Add links to related concepts (Use Case, Use Case Tree, Ontology,
Concept, Story, Composable Business)
- Transform brief content into structured, comprehensive documentation
- Ensure all lines under 70 characters
- Add summary block for consistency with other concept pages
- Add tabbed content structure (Business & Management Audience,
Data & Tech Audience)
- Expand Business & Management Audience tab:
- Add What Is an Ontology? section
- Add The Role of Ontologies in the Data Economy section explaining
demand vs supply
- Add tip admonition about common language
- Add Why Ontologies Matter section
- Significantly enhance Data & Tech Audience tab:
- Add What Is an Ontology in the EKG Method? section
- Add Ontologies as Intermediaries section
- Add How Ontologies Bridge the Gap section explaining semantic
matching
- Add Ontology Standards section (OWL, SHACL, RDFS) with proper
list formatting
- Add Relationship to Concepts section
- Add Reuse and Standardization section
- Add Relationship to Other Concepts section
- Fix list formatting in Ontology Standards section for better
readability
- Add links to related concepts (Use Case, Data Product, Concept,
Persona)
- Transform brief paragraphs into structured, comprehensive content
- Ensure all lines under 70 characters
…provements Workflow page: - Add Persistent Stateful Workflows section explaining short-duration (real-time, in-memory) vs long-duration (hours, weeks, months) workflows - Add Workflows as First-Class EKG Objects section explaining persistence, inspectability, and AWS Step Functions comparison - Add Provenance info admonition explaining PROV-O, Activity/Agent/Entity, and linking Activities to Story execution in Workflow context - Add Observability tip admonition explaining OpenTelemetry/OTLP spans aligning with PROV-O Activities and Workflow-step execution - Add bidirectional relationship explanation: for each Story, we know which Workflows it participates in as a Step - Add hyperlinks to PROV-O, OpenTelemetry, OTLP, and AWS Step Functions - Fix list formatting: add blank lines above all lists for proper vertical bullet rendering Story page: - Add Relationship to Workflows section explaining bidirectional relationship and benefits (reuse analysis, impact analysis, discovery) - Add Workflows to Relationship to Other Concepts list Both pages: - Ensure all lines under 70 characters
Split grid cards into two separate grids: - First grid: Plan, Build, Run phase cards - Second grid: Step cards for each phase This ensures step cards always render in the second row regardless of content size or screen width, preventing layout issues where step cards appear in the first row.
- Add Open Graph and Twitter Card meta tags via template override - Add JSON-LD structured data (Schema.org) for better search visibility - Add page-specific meta descriptions to key pages (outcome, use-case, persona, index) - Add robots.txt file for search engine crawler guidance - Add SEO guide documentation for content authors - Include keywords and schema_type support in page frontmatter This improves social media sharing, search engine understanding, and provides better page-specific descriptions for improved click-through rates.
…vertical position
…core EKG Method concepts
- Add page-specific descriptions, keywords, and schema types to all concept pages - Add SEO metadata to all objective pages (14 pages + index) - Add SEO metadata to all process detail pages (plan: 5, build: 6, run: 4) - Add SEO metadata to all vocabulary pages (8 pages) - Add SEO metadata to intro, FAQ, and other index pages All 55 pages now have unique meta descriptions, keywords, and appropriate schema types for improved search engine visibility and social media sharing.
…e site_name in mkdocs.yml\n- Replace visible ‘EKG Method’ and ‘EKG/Method’ with ‘Use Case Tree Method’ across docs\n- Preserve ‘EKG method’ in keywords for SEO continuity
- Add visual headers with background images for Plan, Build, Run phases - Replace icons with compass, tools, and rocket-launch symbols - Add phase subtitles (Strategy & Scope, Executable Models, Operate & Optimize) - Remove top padding and separator lines for cleaner appearance - Tighten whitespace below headers from 0.9rem to 0.5rem - Override Material theme padding with specific selectors - Maintain proper card grid layout (3 columns)
- Decrease header bottom margin from 0.5rem to 0.25rem - Create tighter, more compact card layout
Remove 'Was this page helpful?' feedback widget and Giscus reactions/comments from all MkDocs pages for a cleaner user experience.
dependabot
bot
force-pushed
the
dependabot/github_actions/actions/checkout-6
branch
from
6a23722 to
20e9ed0
Compare
- Add the benchmark repo to the ekg-method multi-root VS Code workspace for easier cross-repo navigation. - Stop passing --verbose to mkdocs gh-deploy in docs-deploy target to avoid noisy CI logs while preserving deploy behaviour.
Replace dynamic dark/light theme switching with consistent branding: - Use 'base' theme with EKGF blue (#4051b5) for node fills - Use EKGF orange (#ff6f00) for borders and connectors - White text on colored backgrounds for readability - White canvas background for connector visibility This ensures diagrams maintain consistent brand identity regardless of user's light/dark mode preference.
Remove custom dark mode toggle scripts that are no longer needed: - images_dark.js - refresh_on_toggle_dark_light.js These are superseded by the new consistent Mermaid theme configuration that works independently of light/dark mode.
- Remove mkdocs-mermaid2-plugin in favor of Material for MkDocs native support - Configure custom theme colors (indigo primary, orange accent) - Add CSS overrides for Mermaid diagrams to use EKGF blue/orange scheme - Fix instant loading compatibility issues with Mermaid rendering - Node backgrounds: indigo blue (#4051b5) - Borders and connector lines: EKGF orange (#ff6f00) - Text on nodes: white for contrast
…nfig - Remove redundant Model tab from persona.md (consolidated into Ontology tab) - Delete persona-class-diagram.puml source file (no longer needed) - Add mermaid.js configuration with EKGF brand colors (#4051b5, #ff6f00)
- Remove mkdocs-mermaid2-plugin from dependencies (conflicts with Material's native support) - Add Mermaid.js configuration file with EKGF brand colors - Enhance CSS selectors for comprehensive Mermaid diagram styling (indigo blue boxes, orange links) - Switch GitHub Actions runner from macOS to Ubuntu (faster, more cost-effective) - Update Python version to 3.14 in CI workflow - Fix Makefile to properly skip Homebrew on Linux - Update lockfile after dependency changes
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v4...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/github_actions/actions/checkout-6
branch
from
20e9ed0 to
54292ed
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps actions/checkout from 4 to 6.
Release notes
Sourced from actions/checkout's releases.
... (truncated)
Changelog
Sourced from actions/checkout's changelog.
... (truncated)
Commits
1af3b93update readme/changelog for v6 (#2311)71cf226v6-beta (#2298)069c695Persist creds to a separate file (#2286)ff7abcdUpdate README to include Node.js 24 support details and requirements (#2248)08c6903Prepare v5.0.0 release (#2238)9f26565Update actions checkout to use node 24 (#2226)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)