-
Notifications
You must be signed in to change notification settings - Fork 357
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
Update theme goodskin #8016
base: trunk
Are you sure you want to change the base?
Update theme goodskin #8016
Conversation
After submitting Goodskin to WordPress.org, I got a number of comments, some of which I was able to address. The others are listed below. Warnings Skip Links Check skip links requirement here. https://make.wordpress.org/themes/handbook/review/required/#skip-links Extras Broken block found in the editor, https://i.rankmath.com/i/3sz1z4 Translation |
Preview changesI've detected changes to the following themes in this PR: Goodskin. You can preview these changes by following the links below: I will update this comment with the latest preview links as you push more changes to this PR. |
I'm curious why this PR is already out of date with trunk, and needs a rebase. Bea did you pull latest changes before making this update? As for the changes in particular, I'll unfortunately have to ask for help from @vcanales, @madhusudhand, @mikachan or @matiasbenedetto. Did Bea use CBT wrong here, as far as the templates that were put in the patterns directory? Or is there a CBT fix to make? |
I do not use the GH desktop app. What I did was download the latest version of the theme, add it to WP Playground, save my changes and export to a new PR 🤔 |
The best way to ensure that PRs for previews work well is to get the latest code from GitHub, because we could have made changes to a theme without deploying them, which is what I think happened in this PR. @beafialho would it be possible to create another PR following a workflow where the changes you make to the theme are made to the latest code stored GitHub? I'm asking because the conflicts we see here make it hard to determine what to keep. If you need any help figuring out a workflow that will make it easier to review your themes, please reach out to me here on in private! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the theme already in trunk
, it should be showing differences of files such as style.css
, theme.json
But it shows them as new changes.
@beafialho can you try merging latest trunk into this branch?
faf8640
to
2888040
Compare
@jasmussen can you suggest on the following review comment from dotOrg?
|
Resolved conflicts and addressed dotOrg feedback. |
Thanks so much. I'll need to ask some folks about the Midjourney issue. |
Thanks for looking into this @jasmussen . Please share the outcome on a p2 or somewhere with broader visibility! |
Addresses comments from: https://themes.trac.wordpress.org/ticket/185480