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

chore(vscode i18n): update French pack #393

Merged
merged 2 commits into from
Sep 9, 2022
Merged

Conversation

Jose-Matsuda
Copy link
Contributor

Description

CLOSES #387

Tests / Quality Checks

Are there breaking changes?

Ask yourself the next question;

  • Do we want to maintain the previous image from which we had to do breaking changes from?

If no, then carry on. If yes, there is a breaking change and we want to maintain the previous image do the following

  • Create a new branch for the current version (ex v1) based off the current master/main branch
  • Increment the tag in the CI for pushes to master/main (v1 to v2)
  • Change the CI that on pushes to the newly created "v1" branch (the name of the newly created branch we want to maintain is) it will push to the ACR.

Automated Testing/build and deployment

  • Does the image pass CI successfully (build, pass vulnerability scan, and pass automated test suite)?
  • If new features are added (new image, new binary, etc), have new automated tests been added to cover these?
  • If new features are added that require in-cluster testing (e.g. a new feature that needs to interact with kubernetes), have you added the auto-deploy tag to the PR before pushing in order to build and push the image to ACR so you can test it in cluster as a custom image?

JupyterLab extensions

  • Are all extensions "enabled" (jupyter labextension list from inside the notebook)?

VS Code tests

  • Does VS Code open?
  • Can you install extensions?

Code review

  • Have you added the auto-deploy tag to your PR before your most recent push to this repo? This causes CI to build the image and push to our ACR, letting reviewers access the built image without having to create it themselves
  • Have you chosen a reviewer, attached them as a reviewer to this PR, and messaged them with the SHA-pinned image name for the final image to test on the dev cluster (e.g. k8scc01covidacrdev.azurecr.io/jupyterlab-cpu:746d058e2f37e004da5ca483d121bfb9e0545f2b)?

@Jose-Matsuda Jose-Matsuda added the auto-deploy Trigger manual CI steps for this PR label Sep 7, 2022
@Jose-Matsuda
Copy link
Contributor Author

Jose-Matsuda commented Sep 7, 2022

Yup it all appears to work just fine, use k8scc01covidacr.azurecr.io/jupyterlab-cpu:6ebd480b when testing.

Will just clean up tomorrow, removing auto-deploy tag so we don't push needlessly.

Screenshots (EN still works)
image
image

(FR)
image
image

@Jose-Matsuda Jose-Matsuda removed the auto-deploy Trigger manual CI steps for this PR label Sep 7, 2022
@rohank07 rohank07 self-requested a review September 8, 2022 19:52
Copy link
Contributor

@rohank07 rohank07 left a comment

Choose a reason for hiding this comment

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

lgtm!

@Jose-Matsuda Jose-Matsuda merged commit 3a09cd3 into master Sep 9, 2022
@Jose-Matsuda Jose-Matsuda deleted the update-vscode-fr-pack branch September 9, 2022 12:16
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.

Update code-server French translation
2 participants