Crowdin-2019-10-04 [DE,FR,RU] #98
No reviewers
Labels
No Label
Priority-high
Accepting-merge-requests
API
API-dependency
Backport
Blocked
Brainstorming
Breaking
Bug
Changelog
CI
Cleanup
Confirmed
Discussion
Documentation
Duplicate
Enhancement
External-dependecy
F-droid
Feature
Google-play
Improvement
Invalid
Investigate
LGTM-done
LGTM-need
Long-term
Major-release
Minor-release
Needs-cleanup
Needs-feedback
Needs-help
Priority-critical
Priority-low
Priority-medium
Question
Ready
Refactor
Regression
Release
Repository
Security
Suggestion
Support
Testing
Translation
UI/UX
Upstream
Website
WIP
No Milestone
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitnex/GitNex#98
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "6543/GitNex:crowdin"
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?
[x] config file of crowdin[ ] add Arabic lang to Settings-> PR mmarif/GitNex#99@mmarif can you give me rights to asign Labels - would be helpful
-> this PR need consensus if we should iclude the crowdin config file without api key
Future Crowdin PR wont have this includet.
I'll creat crowdin-$date branches with same as PR title in futer ... ok?
crowdinto Crowdin [conf] [lang update]Crowdin [conf] [lang update]to [WIP] Crowdin [conf] [lang update]Seems like crowdin.yml is part of the PR. Maybe you missed the ignore part in the terminal?
That would be helpful.
I would like to but I have not used Github/Gitea structure of access. I was used to GitLab and know how to do that.
Do you have any walk through to guide here.
you can creat an organisation and manage teams who you can asign rights ...
you can add me as member to the project repo and give me permissions ... (look at)
Some Org Conf Pitures for you @mmarif: https://cloud.obermui.de/s/EykWR8sX9YTakrd
We should not expose the API key in the project as it is public. Keys are normally used in the CI etc which is hidden from public to access resources.
Also I believe crowdin.yml we can keep it in our local repository for now.
If I create new org, then I have to move the project from my namespace
mmarif
to that org, which will make things complicated. So adding more people as collaborator is fine.You will have write access to the project now.
[WIP] Crowdin [conf] [lang update]to Crowdin-2019-10-04 [DE,FR,RU]@mmarif you can review and aprove :) 🚀
@6543 done. Do you have the access to merge?
works ... new update is on the horizon somebody is translating the Fr lang :)
Ohh, that's great. 👍