Skip to content

Conversation

@versecafe
Copy link
Contributor

Popping back over to do some cleanup. Moves onto astro 5 and tailwind 4, adds a few best practices in, moves to the more supported bun text lock, and does some small type fixes.

@versecafe
Copy link
Contributor Author

turns out withastro@v2 still looks for the old bun.lockb and ignores the packageManager field in package.json, but this can be solved with an extra line of config in the action added in 02ee6bd

@gmta
Copy link
Contributor

gmta commented Jun 6, 2025

As mentioned on Discord: can you please make sure your commits are atomic? E.g. combine a dependency update with the required fixes to our code to make it work.

For your commit messages, please use the category: change format.


test("Pages Rendered", () => {
mdFiles.forEach((file) => {
for (const file of mdFiles) {
Copy link
Contributor

@trflynn89 trflynn89 Jun 6, 2025

Choose a reason for hiding this comment

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

Please write some notes in the commit message as to why these are best practices. The for loops feel like 6 of one, half a dozen of the other to me.

"Segoe UI Symbol", "Noto Color Emoji";
}

@keyframes marquee {
Copy link
Contributor

Choose a reason for hiding this comment

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

To expand on Jelle's comment about atomic commits - that means fixes like these should be squashed into the original commit that introduced the mistake, i.e. the tailwind v4 commit.

@versecafe
Copy link
Contributor Author

moved to #156 with atomic commits

@versecafe versecafe closed this Jun 6, 2025
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.

3 participants