9
13
Fork
You've already forked keyoxide-docs
23

First stab on translating Keyoxide docs #18

Open
Ryuno-Ki wants to merge 1 commit from Ryuno-Ki/keyoxide-docs:initial-german-translation into main
pull from: Ryuno-Ki/keyoxide-docs:initial-german-translation
merge into: keyoxide:main
keyoxide:main
keyoxide:new-claim-eveonline-143
keyoxide:add-guide

I looked at the French translation files and picked the same for this.
I'm not quite sure how links should be handled.

Are not-yet-translated files not ready for translation yet? As in,
subject to change so it would be a waste of time to translate them
already?

Signed-off-by: André Jaenisch andre.jaenisch@posteo.de

I looked at the French translation files and picked the same for this. I'm not quite sure how links should be handled. Are not-yet-translated files not ready for translation yet? As in, subject to change so it would be a waste of time to translate them already? Signed-off-by: André Jaenisch <andre.jaenisch@posteo.de>
First stab on translating Keyoxide docs
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
b964b1b3f8
 
I looked at the French translation files and picked the same for this.
I'm not quite sure how links should be handled.
Are not-yet-translated files not ready for translation yet? As in,
subject to change so it would be a waste of time to translate them
already?
Signed-off-by: André Jaenisch <andre.jaenisch@posteo.de>
Owner
Copy link

Hey, thanks for the PR :) I really hope there won't be any more changes to the documentation structure. In the worst case scenario, we'll move the files around a bit but the content is pretty solid now IMO.

Shall I try and merge this one already? Or do you want to add more to this PR?

Hey, thanks for the PR :) I really hope there won't be any more changes to the documentation structure. In the worst case scenario, we'll move the files around a bit but the content is pretty solid now IMO. Shall I try and merge this one already? Or do you want to add more to this PR?
Author
Owner
Copy link

This PR is ready to be merged.
I was mainly concerned whether I got the format and file structure right.

Another PR would translate the remaining files up to the point of branching.

This PR is ready to be merged. I was mainly concerned whether I got the format and file structure right. Another PR would translate the remaining files up to the point of branching.
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
This pull request has changes conflicting with the target branch.
  • config.toml
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u initial-german-translation:Ryuno-Ki-initial-german-translation
git switch Ryuno-Ki-initial-german-translation

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff Ryuno-Ki-initial-german-translation
git switch Ryuno-Ki-initial-german-translation
git rebase main
git switch main
git merge --ff-only Ryuno-Ki-initial-german-translation
git switch Ryuno-Ki-initial-german-translation
git rebase main
git switch main
git merge --no-ff Ryuno-Ki-initial-german-translation
git switch main
git merge --squash Ryuno-Ki-initial-german-translation
git switch main
git merge --ff-only Ryuno-Ki-initial-german-translation
git switch main
git merge Ryuno-Ki-initial-german-translation
git push origin main
Sign in to join this conversation.
No reviewers
Labels
Clear labels
Contribution welcome
Get started contributing here
Good first issue
Good if you are new to the project or to open source contributions
Impact
External
 Affects the people using the project
Impact
Internal
 Affects on the people working on the project
Priority
Critical
 Work on right now
Priority
High
 Work on at earliest convenience
Priority
Low
 Work on in spare time
Priority
Medium
 Work on regularly
Review
Duplicate
 Already exists
Review
Off Topic
 Does not fall within the scope of the repo/project
Status
Backlog
 Is not being worked on yet
Status
Blocked
 Is waiting on something or someone
Status
Completed
 Is done
Status
In Progress
 Is being worked on
Status
Investigating
 Is waiting on research or questions
Status
Needs Decision
 Is waiting on a decision by the devs/contributors
Status
Needs Info
 Is waiting on additional information before it can be solved
Status
Needs Triage
 Is new issue that needs reviewing
Status
Testing
 Is being checked and verified
Status
Waiting For Review
 Is waiting on reviewers to approve
Status
Won't Fix
 Won't be fixed
Type
Bug
 Related to something not working as intended
Type
CI
 Related to continuous integration
Type
Documentation
 Related to documentation
Type
Enhancement
 Related to a new feature or an improved one
Type
New Claim
 Related to a new identity claim/proof
Type
Security
 Related to security
Type
Tests
 Related to code tests
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
keyoxide/keyoxide-docs!18
Reference in a new issue
keyoxide/keyoxide-docs
No description provided.
Delete branch "Ryuno-Ki/keyoxide-docs:initial-german-translation"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?