-
Notifications
You must be signed in to change notification settings - Fork 3k
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 MTE-1885 [v122] Move scripts and other files to firefox folder #17310
Refactor MTE-1885 [v122] Move scripts and other files to firefox folder #17310
Conversation
firefox-ios/l10n_comments.txt
Outdated
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.
Not sure if we can even remove this file... it has not been updated in two years
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.
@Delphine do you know what this is used for?
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.
No idea. @boek Do you remember this?
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.
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.
oh I see, thanks @lmarceau ... should I move it then or wait for another round of changes? Not sure I can create a PR in LocalizationTools repo or to handle that change there
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 think I can create a PR in there. The strings for v120 are currently being exported, so if we merge the current PR (17310) after that's done to avoid breaking l10n flow would be ok I think (should be done by end of week for sure) 👍 I just created a task for myself to adjust the script in LocalizationTools once this PR is merged.
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.
that sounds great :) thanks!
firefox-ios/import-strings.sh
Outdated
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.
@flodolo as commented on focus-ios PR, I'm also moving this script here. I have changed the path in the bootstrap file where it is executed. Locally I get the import working, but please let me know if I'm missing any other changes that could break the automation around this.
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.
@flodolo I also changed the name for the focus github action and seems that this change is not affecting anything, but doublechecking
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.
No risk, we have our own workflow, we only use scripts from this repo.
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.
We should be good, since we use LocalizationTools to do the actual extraction
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.
No risk, we have our own workflow, we only use scripts from this repo.
firefox-ios/l10n_comments.txt
Outdated
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.
@Delphine do you know what this is used for?
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.
@relud is it fine if we rename this?
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.
yes
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.
@lmarceau checking with you if we can rename as author of the github action
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.
Yes should be safe to rename 👍
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.
@lmarceau checking with you if we can rename as author of the github action
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.
Yes should be safe to rename 👍
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.
@jeddai checking with you if we can rename without breaking anything as author of the github action
I double-checked one of these comments, and we still have it in the XLIFF file. So, something is using this file, but I have no clue how based on #8050 |
And that's because the file is used from code that lives elsewhere, and needs to be updated as well |
Client.app: Coverage: 32.51
Generated by 🚫 Danger Swift against 71cf099 |
Thanks for checking, I will not remove the |
This pull request has conflicts when rebasing. Could you fix it @isabelrios? 🙏 |
743d77b
to
4f9b3d7
Compare
I had to create a firefox-ios-tests folder inside firefox-ios and move the tests there. The way I created firefox-ios folder before would not allow me to move app folders in it in the future. This PR is ready for review. Thanks for your comments so far. |
@flodolo I'm moving the import-strings.sh script into firefor-ios folder. I have changed the bootstrap script to run it using the new location. Are there more changes needed so that the import/export keeps working? The import is working for me locally, but double checking as I don't want to break things |
We only use the bootstrap from this repo and LocalizationTools on our side. Once this is merged, you should verify that the import action works correctly in this repo. |
I will verify that for sure, thank you |
FYi, This PR will not land until the v121 branch is cut from main on Monday to disrupt the less possible |
This pull request has conflicts when rebasing. Could you fix it @isabelrios? 🙏 |
😬 Would Sync Integration Tests run? I can give it a try. |
In theory yes, on MacStadium I will fix the path to the test results once this lands |
🎉 I just confirmed that the |
I take it back. The TPS logs shows the following errors. @isabelrios Could you please update the paths to files needed by TPS?
|
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.
Please check paths for sync integration tests. 🙇🏼
@clarmso I have a copy of my branch on MacStadium and the tests passed there. It may be something on your virtual env that is chached? |
😓 |
6125091
to
55afc47
Compare
This pull request has conflicts when rebasing. Could you fix it @isabelrios? 🙏 |
55afc47
to
c5ebd8e
Compare
This pull request has conflicts when rebasing. Could you fix it @isabelrios? 🙏 |
c5ebd8e
to
65abf87
Compare
This pull request has conflicts when rebasing. Could you fix it @isabelrios? 🙏 |
65abf87
to
023fafa
Compare
📜 Tickets
Jira ticket
Let's move more files into firefox-ios folder.
Also let's rename the github actions mobile test eng own.
📝 Checklist
You have to check all boxes before merging