Conversation
- Added package.json for project dependencies and scripts - Included tsconfig.json for TypeScript configuration
…ssues - Documented permission errors when publishing packages. - Explained the impact of squashed commits on semantic-release. - Provided guidance on resolving `reference already exists` errors when pushing tags. - Added instructions for recovering from lost releases after `git push --force`. feat: create CI configuration guide for semantic-release - Outlined the importance of running semantic-release after all tests pass. - Listed CI services that support this configuration. - Explained authentication requirements for pushing to remote repositories. feat: introduce comprehensive configuration documentation - Detailed the configuration options available for semantic-release. - Explained how to set up configuration files and CLI arguments. - Provided examples for configuring branches, repository URLs, and plugins. feat: establish getting started guide for semantic-release - Created a step-by-step guide for installing and configuring semantic-release. feat: outline installation methods for semantic-release - Recommended global installation via npx for CI environments. - Discussed the implications of local installation and dependency management. feat: document plugins and their configuration in semantic-release - Explained the role of plugins in the release process. - Listed default plugins and how to install additional ones. - Provided examples of plugin declaration and execution order. feat: introduce shareable configurations for semantic-release - Explained the concept of shareable configurations and how to use them. feat: detail release workflow configuration for semantic-release - Described the management of complex release workflows with multiple branches. - Explained branch types and their properties for effective release management.
…ved navigation order
- Refactor the highlights section in intro.md for better readability. - Update CI configurations index.md to improve formatting. - Enhance git authentication SSH keys documentation for clarity. - Standardize formatting in git-hosted services index.md. - Improve distribution channels recipe formatting for consistency. - Refine release workflow recipes for better structure. - Update FAQ.md for improved clarity and consistency. - Enhance resources.md with better formatting for video and article lists. - Improve CI configuration documentation for better readability. - Standardize configuration documentation for semantic-release options. - Update installation.md for clearer instructions on global installation. - Refactor plugins.md for better readability and structure. - Enhance workflow-configuration.md for improved clarity and consistency.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
initial suggestion before diving deeper: lets avoid |
travi
left a comment
There was a problem hiding this comment.
this all looks good to me.
i havent tried to start it locally to see it rendered. is that the simplest way to see how things look? looking forward to getting hosting setup so we could have a PR preview deploy to take a look at
the one question i have is whether the embedded styles and js could be extracted to separate files or not. i'm not up to speed on astro or tailwind, so you might tell me that it is common convention in those cases, but i still prefer separate files if that does conflict with things
There was a problem hiding this comment.
interesting update to the logo :D
There was a problem hiding this comment.
We already are deployed actually... currently sharing the @hearts vercel account pending the while we get a pro account from Vercel.... and the preview for this particular PR is https://semantic-release-docs-git-feat-new-hearts.vercel.app/
Link's in the Preview text on the vercel's PR comment
There was a problem hiding this comment.
Link's in the Preview text on the vercel's PR comment
🤦🏼 totally overlooked that comment, haha. thanks for the clarity
…d is set to false in index.mdx
The embedded style/js-script is kinda convention for More like how interactivity is contained in a YES of-course you can externalise and import but while you can |
This pull request introduces a major reorganization and modernization of the documentation site, shifting from gitbook to a more non-service tied and custom framework by implementing @withastro and integrating @astrojs/starlight.
Other Changes
lintgithub workflow for code qualityScreencast/Screenshot
screen-capture.28.webm