Skip to content

chore: adapt landingpage content#305

Merged
me-marcel merged 1 commit intomainfrom
chore/adapt_landingpage_content
May 1, 2026
Merged

chore: adapt landingpage content#305
me-marcel merged 1 commit intomainfrom
chore/adapt_landingpage_content

Conversation

@me-marcel
Copy link
Copy Markdown
Member

Pull Request

Current Behavior

Expected Behavior

Related Issue(s)

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📚 Documentation update
  • 🔧 Refactoring (no functional changes, no api changes)
  • ⚡ Performance improvement
  • 🧪 Test improvements
  • 🎨 Style/formatting changes
  • 🔒 Security improvements

Checklist

Code Quality

  • Code follows the project's style guidelines
  • Self-review of code has been performed
  • Code is commented, particularly in hard-to-understand areas
  • Corresponding changes to documentation have been made
  • Changes generate no new warnings

Testing

  • New and existing unit tests pass locally
  • Tests have been added that prove the fix is effective or that the feature works
  • All affected projects build, test, and lint successfully
  • E2E tests have been run (if applicable)

Compliance

  • All commits use conventional commit format (e.g. feat:, fix:, docs:)
  • Application and library boundaries and dependencies are valid
  • Code follows the project’s style and quality practices
  • Nx is used for build, test, and lint (e.g. nx prepush, nx affected)

Documentation

  • Relevant docs and READMEs have been updated to reflect changes
  • API or public contract changes are documented (if applicable)

Additional Notes

Reviewer Guidelines

  • Please ensure all checklist items are verified
  • Pay special attention to breaking changes and their impact
  • Verify that all tests pass and code quality standards are met
  • Check that documentation is updated appropriately

Questions or concerns? Contact the development team at hi@forepath.io

@me-marcel me-marcel self-assigned this May 1, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 1, 2026

Code Coverage

apps/frontend-portal100.00%✅ 0.00%
Coverage Report
File % Stmts % Branch % Funcs % Lines Uncovered Line #s
All files   100   100   100   100  
 ...component.html   100   100   100   100  
 app.component.ts   100   100   100   100  

libs/domains/framework/frontend/feature-portal0.00%✅ 0.00%
Coverage Report
File % Stmts % Branch % Funcs % Lines Uncovered Line #s
All files   0   0   0   0  

@me-marcel me-marcel merged commit cc6cbf2 into main May 1, 2026
15 checks passed
@me-marcel me-marcel deleted the chore/adapt_landingpage_content branch May 1, 2026 10:17
forepath-semantic-release Bot pushed a commit that referenced this pull request May 1, 2026
## [1.51.0](v1.50.0...v1.51.0) (2026-05-01)

### Features

* ai feature prototyping skill ([#300](#300)) ([5897aa9](5897aa9))
* chat preservation and extended environment management ([#303](#303)) ([f83a968](f83a968))
* page content management and context injection ([#302](#302)) ([52026b4](52026b4))
* support multi-repo workspace context injection ([#301](#301)) ([387f86a](387f86a))

### Chores

* adapt landingpage content ([#305](#305)) ([cc6cbf2](cc6cbf2))
* vcs message scope rule ([#299](#299)) ([4d02989](4d02989))

### Documentation

* add missing licenses ([#296](#296)) ([bafd339](bafd339))

### Code Refactoring

* extended linting for cleaner code ([#298](#298)) ([5ed41d3](5ed41d3))

### Continuous Integration

* publish sboms to cloudflare r2 ([#297](#297)) ([65cebc6](65cebc6))
@forepath-semantic-release
Copy link
Copy Markdown

This PR is included in version 1.51.0 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant