Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(css): merge CSS Units group into CSS Values and Units #879

Open
wants to merge 43 commits into
base: main
Choose a base branch
from

Conversation

skyclouds2001
Copy link
Contributor

@skyclouds2001 skyclouds2001 commented Jan 4, 2025

Description

merge CSS Units group and other unit-related groups into, this follows the structure of the specification and mdn web docs

https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Values_and_Units
https://drafts.csswg.org/css-values/
https://drafts.csswg.org/css-values-5/

Motivation

Additional details

Related issues and pull requests

@skyclouds2001 skyclouds2001 marked this pull request as ready for review January 4, 2025 14:55
@skyclouds2001 skyclouds2001 requested a review from a team as a code owner January 4, 2025 14:55
@skyclouds2001 skyclouds2001 requested review from pepelsbey and removed request for a team January 4, 2025 14:55
@github-actions github-actions bot added the idle Issues and pull requests with no activity for three months. label Feb 14, 2025
Copy link
Member

@pepelsbey pepelsbey left a comment

Choose a reason for hiding this comment

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

I noticed the removal of the .github/workflows/codeql.yml is not mentioned/justified in the description, and there are many other changes, too. It seems like the other feature branch (next) got merged here and widened the scope of the PR.

@pepelsbey pepelsbey removed the idle Issues and pull requests with no activity for three months. label Feb 24, 2025
@skyclouds2001
Copy link
Contributor Author

I noticed the removal of the .github/workflows/codeql.yml is not mentioned/justified in the description, and there are many other changes, too. It seems like the other feature branch (next) got merged here and widened the scope of the PR.

guessing that happens due to unexpected merge/rebase

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