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

Titan angled waist #3493

Open
wants to merge 9 commits into
base: develop
Choose a base branch
from
Open

Conversation

anna-puk
Copy link
Contributor

@anna-puk anna-puk commented Jan 29, 2023

Do not merge as-is! Also contains the workaround of deleting the sites/org/components/gdpr directory. (fixed)

Introducing a waist angle for titan: center back will be raised and center front lowered. This impacts e.g. charlie as well, in a way that seems to make sense.

@vercel
Copy link

vercel bot commented Jan 29, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
freesewing-lab ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 30, 2023 9:59pm
v2-freesewing-dev ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 30, 2023 9:59pm

@vercel
Copy link

vercel bot commented Jan 29, 2023

@anna-puk is attempting to deploy a commit to the freesewing Team on Vercel.

A member of the Team first needs to authorize it.

@codecov
Copy link

codecov bot commented Jan 29, 2023

Codecov Report

Merging #3493 (cf32c05) into develop (3fcbf56) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #3493      +/-   ##
===========================================
- Coverage    98.44%   98.42%   -0.03%     
===========================================
  Files           15       15              
  Lines         4637     4634       -3     
  Branches       583      582       -1     
===========================================
- Hits          4565     4561       -4     
- Misses          67       68       +1     
  Partials         5        5              
Flag Coverage Δ
core 98.42% <ø> (-0.03%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@BenJamesBen
Copy link
Contributor

I tested the changes in the localhost lab with Titan, Paco, and Charlie, and everything seems to work correctly.

@BenJamesBen
Copy link
Contributor

I briefly retested the updated PR in the lab with Titan, Paco, and Charlie, and things seem to be working okay.

@joostdecock
Copy link
Member

Can we get this out of draft? @BenJamesBen has given their seal of approval, so it seems like we should be ready to move on this. But there's some conflicts and then the comment at the very top asking not to merge this.

So where do we go from here?

@anna-puk
Copy link
Contributor Author

Can we get this out of draft? @BenJamesBen has given their seal of approval, so it seems like we should be ready to move on this. But there's some conflicts and then the comment at the very top asking not to merge this.

So where do we go from here?

This branch also contains a commit that removes the sites/org/components/gdpr directory.

Can we get this out of draft? @BenJamesBen has given their seal of approval, so it seems like we should be ready to move on this. But there's some conflicts and then the comment at the very top asking not to merge this.

So where do we go from here?

This branch also contains a commit removing the sites/org/components/gdpr directory. I just need to revert that commit and then it should be okay to merge.

contents of sites/org/components/gdpr should now match develop
@anna-puk anna-puk marked this pull request as ready for review April 30, 2023 21:38
@anna-puk
Copy link
Contributor Author

I added one extra option and restored the gdpr directory. If it still passes review, please merge! :)

Copy link
Contributor

@BenJamesBen BenJamesBen left a comment

Choose a reason for hiding this comment

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

I re-tested the updated PR, including the new useWaistAngleFor option, and I believe it is ready to be merged for wider testing.

There is no documentation for the new options. We'll want to address that in a separate PR.

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

Successfully merging this pull request may close these issues.

None yet

3 participants