-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Downloading translations and ignoring branch at Crowdin #2592
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2592 +/- ##
==========================================
- Coverage 27.38% 26.96% -0.42%
==========================================
Files 86 87 +1
Lines 17010 17297 +287
==========================================
+ Hits 4658 4664 +6
- Misses 11673 11953 +280
- Partials 679 680 +1
Continue to review full report at Codecov.
|
I don't quite see point in downloading translations from crowdin. As we need to get these translations in git |
Two options, one is manually download crowdin languages packs and send a PR, another is remove all language packs except en-US and download it before build. |
@JonasFranzDEV I like @tboerger idea that appleboy/drone-git-push could be used to push downloaded files to git |
In reference to #2585 (comment) |
.drone.yml
Outdated
image: appleboy/drone-git-push | ||
pull: true | ||
secrets: [ git_push_ssh_key ] | ||
remote: "[email protected]:go-gitea/gitea.git" |
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 we don't need the remote
.drone.yml
Outdated
pull: true | ||
secrets: [ git_push_ssh_key ] | ||
remote: "[email protected]:go-gitea/gitea.git" | ||
branch: master |
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.
The branch should be already master?
.drone.yml
Outdated
|
||
translations: | ||
|
||
github: |
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.
This section seems not related?
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.
@JonasFranzDEV why this section is needed here?
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.
@daviian What should I do for a "full rebase"?
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.
git rebase master
?
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.
@JonasFranzDEV Usually I rebase my master to be the same as upstream/master (original gitea remote) and after checking out my pr branch I do it like @Morlinest said.
* remove orgnization watch repositories * fix migration * fix typo and missing change * remove unused code
…o-gitea#2678) * Allow custom SSH user in UI for built-in SSH server (go-gitea#2617) * Some fixes * Did make fmt * Updated according to review - Renamed config to BUILTIN_SSH_SERVER_USER - Removed unnecessary default string value for config item * Updated according to review * Fixed some minor issues
* Add Activity page to repository * Add request data for activity * Add issue data for activity * Add user unit right checks * Add releases to activity * Log repository unit loading error
…ions (go-gitea#2699) * Fix so that user can still fork his own repository to his organizations * Fix to only use owned organizations * Add integration test for forking own repository to owned organization
* provide both possible authentication solutions Signed-off-by: David Schneiderbauer <[email protected]>
* Create new branch from branch selection dropdown and rewrite it to VueJS * Make updateLocalCopyToCommit as not exported * Move branch name validation to model * Fix possible race condition
* Integration test for activity page * Small code refactoring for acitvity page * Move activity stats calculation logic to model
…2705) * fix plain readme didn't render correctly on repo home page * fix missing render * remove unused template variables
…o-gitea#2710) * Fix PR, milestone and label functionality if issue unit is disabled or not assigned to user * Fix multi-actions in PR page * Change error message * Fix comment update and delete functionality in PR
* merge password and 2fa page on user settings
Signed-off-by: Jonas Franz <[email protected]>
I've fully rebased it onto master. @Morlinest |
I think something is wrong, 51 files changed. |
@JonasFranzDEV Was your pr branch created from master!? |
Replaced by #2727 |
This PR adds the following build steps:
The build steps are splitted because the files should only uploaded to crowdin if all test passes.
It also adds the
ignore_branch
option to fix the build process because gitea does not use branches at crowdin.This is already tested here:
Related to #2585
Related to jonasfranz/drone-crowdin#2