-
Notifications
You must be signed in to change notification settings - Fork 189
refactor: replace capital letters with normal letters on our navbar #296
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
refactor: replace capital letters with normal letters on our navbar #296
Conversation
isabelcosta
left a comment
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.
Thank you so much @ftonato for proposing and working on this!
|
cc @brittanyjoiner15 could you maybe look at this one too :) |
brittanyjoiner15
left a comment
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.
Looks good to me! Left a small comment about alphabetization, but feel free to ignore as it's not essential :) Well done, this was nice @ftonato !
|
@brittanyjoiner15 could you please approve it again :) Approve is one of the review options. After that I can merge :) |
|
@brittanyjoiner15 do you know what could be wrong with prettier run here? I don't think it is related to this PR 🤔 But I am not sure @ftonato do you have an idea of what could be happening here? I updated this PR in hopes it would be mergable right away, but this check is failing. Could we do something here 🤔 |
|
@ftonato @isabelcosta hmm, I wonder if it's because it's confused because we have the |
|
Hello, after a few minutes of trying and trying I found the problem, or at least managed to fix it on my branch. I'll open a pull-request to submit the solution and remove the commits I made on the current branch to test...
|
30b934e to
78f46c4
Compare
|
I just deleted all commits, I'm going to redo them (dumb)! Edit: Done! We can merge this and as I said above I will send another PR to fix the "prettier problem" 😛 |
78f46c4 to
7d7faa6
Compare
We can talk on Zulip :) That is where the community talks about the projects so that everyone can join discussions. We have a stream for this project. |
|
@ftonato can you update the PR, just so we see the checks passing, please? |
9a9e8fe to
7d7faa6
Compare
|
@ftonato do you have any idea why the checks for prettier are failing 🤔 i wonder why 😳 |
|
@isabelcosta so we probably need to update the docs to let people know they'll want to install prettier locally, and they might need to run the |
|
I don't understand why it's failing only on the pull-request and not on my branch (fork), I'll need to invest a little more time on this tomorrow to calmly evaluate... I will do this as soon as possible! |
If that is something we can put on README, let's do it! Could you create an issue to add that instruction to the README? |
I see it falling on your fork as well https://github.com/ftonato/anitab-org.github.io/runs/3919521463 🤔 but take your time! As long as we have updates from time to time. |
|
@isabelcosta yes! i can do that, @ftonato i might want you to be my "beta" tester and confirm if that seems to fix the issue or not before i do that. Basically following these instructions |
|
I made some changes thinking it might have been something and it worked on my branch, but here it kept failing so I pushed it back to the original state (thus failing on my branch too). However, I will try to validate all this today =) |
7d7faa6 to
217b463
Compare
|
@isabelcosta can you take a look on this? It seems that our bot (prettier action) don't have the right permissions to perform the commit: |
|
Not sure why, but it seems the From what I understand, this is failing because it is trying to commit changes for a file that has changes proposed by prettier. I wonder if this action should be changed, to not try to commit but simply fail if prettier suggests changes and pass if prettier does not suggest changes. |
|
@ftonato I see it failing again. I will ignore this for now and test the PR and if all good merge this. |
| uses: creyD/[email protected] | ||
| with: | ||
| prettier_options: "--write src/**/*.{ts,jsx,js,css,html,json,md}" | ||
| prettier_options: --write src/**/*.{ts,jsx,js,css,html,json,md} |
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.
I just noticed, is there any reason why this was reverted and why package-lock.json and yarn.lock have so many changes?
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.
I realized that the quotes are not necessary (and not suggested in the plugin's official documentation) so I removed it!
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.
The package-lock has a lot of changes because I tried to rebase it with develop (it still fails)
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.
Could you revert those file changes (yarn.lock and package-lock.json)? And keep this PR to the changes related to the ticket?
|
@isabelcosta I really don't know why it only fails in PR for this repository, I do it in my FORK it works perfectly, and I really think it might have some relationship with permissions (https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#permissions). My suggestion is to stop using github action to make the prettier and do it with husky, does it sound okay or not? (If approved, I can create the PR with it, but someone from the organization will have to remove the action) |
I understand, we can remove/fix it on another ticket. That is fine! |
|
I will create another PR to include all this changes! (#325) @isabelcosta Can we merge this PR? |

Description
In order to fix the problem related on the issue #295 I've created the code to fix it.
Fixes #295
Type of Change:
How Has This Been Tested?
You can run the new branch and check if all navigation items are with "capital letters".
Checklist:
Delete irrelevant options.