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

Remove legacy localisation script references and actions #2

Conversation

iangmaia
Copy link
Owner

@iangmaia iangmaia commented Jan 29, 2023

EDIT: this PR was re-created in the main repo: wordpress-mobile#447

What does it do?

This is a clean up removing the remainder references to the legacy localisation tooling, following up the #433 PR.

It contains:

  • Removal of the actions ios_localize_project and ios_update_metadata.
  • Removal of the methods localize_project, update_metadata and strings_files on Ios::GitHelper
  • Removal of the parameter include_metadata from the method Ios::GitHelper.commit_version_bump(include_deliverfile:)

Related PRs

  • This PR is built on top of the #433 PR
  • This PR contains @mokagio's draft PR, which can be closed if this is merged.
  • Based on the changes done here, this PR will remove functionality related to the obsolete Deliverfile.

Checklist before requesting a review

  • Run bundle exec rubocop to test for code style violations and recommendations
  • Add Unit Tests (aka specs/*_spec.rb) if applicable
  • Run bundle exec rspec to run the whole test suite and ensure all your tests pass
  • Make sure you added an entry in the CHANGELOG.md file to describe your changes under the approprioate existing ### subsection of the existing ## Trunk section.

mokagio and others added 3 commits January 29, 2023 17:36
We now have newer, better actions to achieve the same results:

- `ios_generate_strings_file_from_code`
- `ios_extract_keys_from_strings_files`
- `ios_download_strings_files_from_glotpress`
- `ios_merge_strings_files`
Copy link

@mokagio mokagio left a comment

Choose a reason for hiding this comment

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

Looking good.

I checked this locally and run the test, which passed.

I didn't go down the route of opening a PR for this on the main repo to trigger CI because I see this is incremental on top of another one and I'd like to know how you plan to merge them.

@@ -7,6 +7,7 @@
### Breaking Changes

- Remove the `skip_glotpress` parameter from the `ios_bump_version_release` action [#443]
- Remove the actions `ios_localize_project` and `ios_update_metadata`
Copy link

Choose a reason for hiding this comment

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

There's no PR number here, but that's to be expected give this PR is on your fork

files_list = [File.join(ENV['PROJECT_ROOT_FOLDER'], 'config', '.')]
files_list = [File.join(get_from_env!(key: 'PROJECT_ROOT_FOLDER'), 'config', '.')]
Copy link

Choose a reason for hiding this comment

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

Nice that you updated this while touching the file, and that it was done in a dedicated commit 👍

@iangmaia
Copy link
Owner Author

Looking good.

I checked this locally and run the test, which passed.

I didn't go down the route of opening a PR for this on the main repo to trigger CI because I see this is incremental on top of another one and I'd like to know how you plan to merge them.

Thanks @mokagio 👍

My plan is: once wordpress-mobile#443 gets merged, I'll target this PR to the main repo's trunk, but pleas let me know if you have other ideas or if another process is preferred.

@AliSoftware
Copy link

Just merged wordpress-mobile#443 🙂

@iangmaia iangmaia deleted the branch cleanup/remove-skip-glotpress-issue-372 January 30, 2023 21:07
@iangmaia iangmaia closed this Jan 30, 2023
@iangmaia
Copy link
Owner Author

iangmaia commented Jan 30, 2023

Ah, just noticed that you can't switch forks when editing the Pull Request (which makes sense, the PRs are for a repo), only branches... Anyway, I'll just create another one for this branch to the main repo now that 443 has been merged 🙂

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