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

[TEST] Update JA gitbook with latest from main #454

Closed
wants to merge 125 commits into from
Closed

[TEST] Update JA gitbook with latest from main #454

wants to merge 125 commits into from

Conversation

spier
Copy link
Member

@spier spier commented Sep 15, 2022

Goal: Publish the latest changes to the Japanese translation.

Note: Currently we are doing this manually. Eventually we want to automate it. Expect some bumps in the road :)

spier and others added 19 commits July 28, 2022 11:38
Also linking to the translation documentation.
Improve docs of book/translation/contribution
Introduce lychee link checker (to fix issues with rate limiting on checks of github links with old liche link checker).
Uses a more explicit link ignore list in `.lycheeignore` which is easier to understand.

Adding some badges for this GHA and others to the README (for fun).
Also giving this GHA a simpler name: Link Check
* Add Airbus as know instances of the InnerSource Portal pattern
Pattern "Extensions to Manage Contributions at Scale" 

Co-authored-by: Sukriti-Sharma4 <[email protected]>
Co-authored-by: Gabe Goodhart <[email protected]>
Co-authored-by: Alex Brooks <[email protected]>
* Move all Japanese files to folder translation/ja
* JA book will now be generated from all 'book-ja*' branches
* Change TOC generation script to pickup things from translation/ja folder
* Improvements to the docs of the translation process
@spier spier changed the title Updated JA gitbook with latest from main [TEST] Update JA gitbook with latest from main Sep 16, 2022
@spier
Copy link
Member Author

spier commented Sep 16, 2022

Hmm. I don't know why we are ending up with conflicting files here.

Possibly because I did "rebase and merge" to update the branch the last time in #445 ?

@spier
Copy link
Member Author

spier commented Sep 18, 2022

The book-ja branch is a long-lived branched (previously the name was book-jp but it is the same branch).

Both in this PR here, as well as in #445 I merged main into book-ja.

I had expected that this PR would not have any conflicts and just be "ready to merge" as is.
However this PR surprized me in two ways:

  1. I see commits that were already merged previously. See picture below.
  2. There are conflicts that need to be resolved before merging.

I don't know why that happens.

I should mention that we have a GitHub Action that runs on the book-ja branch, which will create a new commit that does not exist on main. Possibly that is contributing to the issue?

Duplicate commits, i.e. commits that should already exist on the book-ja branch, are:

Screenshot 2022-09-18 at 09 14 43

Copy link
Member

@yuhattor yuhattor left a comment

Choose a reason for hiding this comment

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

lgtm

Add metrics to "employee satisfaction & talent retention"
@spier spier added the Type - Translation Translating patterns into other languages label Sep 22, 2022
yuhattor and others added 28 commits June 18, 2023 14:24
Airbus switched from SAP portal to Backstage/Bazaar as Backstage is becoming the standard internally
Co-authored-by: bakisunsan <[email protected]>
Create COMMUNICATION-template.md - Creating template so I have link to add to the base documentation pattern when I add the template to it.

---------

Co-authored-by: Sebastian Spier <[email protected]>
…-sustainable-growth-ja-translation

Japanese Translation - Extensions for Sustainable Growth Pattern
* Use glob to select files to be checked by vale
* Removing GH token
* Remove unused gitignore rule
* Adding debug flag, to increase inspectability of vale output in future GHA runs
Bumps [semver](https://github.com/npm/node-semver) from 5.7.1 to 5.7.2.
- [Release notes](https://github.com/npm/node-semver/releases)
- [Changelog](https://github.com/npm/node-semver/blob/v5.7.2/CHANGELOG.md)
- [Commits](npm/node-semver@v5.7.1...v5.7.2)

---
updated-dependencies:
- dependency-name: semver
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Adding configuration for the welcome bot.
* Update link to the ISC slack instance.
* Stop checking link to chatham house rule (as it always gets reported as broken, even though it is not).
Move Release Process to structured by doing various changes:

* Update title
* Update problem category (in the mindmap). Also added Standard Base Documentation to this new problem category.
* Updates to Context and Force. Plus a few grammar clean ups
* Update Patlet
* Restructure Problem and Context
Merging without review, as the review happens on a different repo.
* Updated Japanese translation - innersource-portal.md
* Updated Japanese translation - maturity-model.md
* Checked Japanese translation - contracted-contributor.md
* Update translation history
* Checked Japanese translation - document-your-guiding-principles.md
* Japanese translation - Checked files that do not need to be updated and update the update date
* Check the i18n 🇨🇳 consistency
* Remove individual names from consistency check-only update information
* Inserted new-line to pass the lint checker
* Update the updated date
@spier
Copy link
Member Author

spier commented Aug 26, 2023

Deleting old branch, as the book release for other languages doesn't work well like this anyways.
Will be using a new approach soon, using gitbooks new "monorepos" configuration (see #578).

@spier spier closed this Aug 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type - Translation Translating patterns into other languages
Projects
None yet
Development

Successfully merging this pull request may close these issues.