Crowdin GH native integration and GH Action

[Nukecraft5419]

Hi, but doesn't Crowdin normally already automate everything via the integration between Crowdin and GitHub I am asking whether or not I should also include this automation in the repository

[dies]

Github Action is more of an alternative way to integrate with Crowdin than the native integration. It doesn't require you to give Crowdin access to your repo, it has some more features and flexibility, like configuring who will review pull requests. However, Github Action may be more difficult to set up for some users.

[Nukecraft5419]

So if I'm not mistaken Crowdin has the limit of 1 integration for the free plan on that I still don't understand if like on another crowdin project always open to the public then it makes me do another automation or not, and if this thing with the bot is a better way to not have that limit

[dies]

There are no limits to open-source projects. You can submit this form to get a license for your open project https://crowdin.com/page/open-source-project-setup-request

Github Action integrations do not count toward the integrations limit

[Nukecraft5419]

I have noticed that with the integration of Crowdin and GitHub I have to go and synchronise myself to get the sine pulls created, it usually doesn't synchronise anything just the first time, in fact I would like to see if then using GitHub Actions this will be resolved for the open-source projects request is a good thing only it requires a site and Crowdin Enterprise in the future will

[dies]

The website field is optional. The Crowdin Enterprise organization handle is also optional. If you're using crowdin.com, just enter your username and you should be good to go

[Nukecraft5419]

What advantages would it provide?

[tatttz]

Open-source provide you with some features that aren't available in the Free plan, moreover if you have public repo, as Serhiy advised you regarding your case

[Nukecraft5419]

It filled itself in for me, i.e. the project part, the username and the email automatically taken from the account I logged in with. Then I put the repository link as the website link and the licence link as the direct link to the licence in the repository, and then as "Your name" I copied what's under the Crowdin username.

[tatttz]

Great! The main requirement is publicly available repo, so please don't forget to share the url to your repo once requesting the open-source licence

[Nukecraft5419]

In fact, I put the repo url in the site url, then I wanted to see if it is possible to get help to switch from integration to integration with GitHub Actions https://github.com/LifeMC-Studios/LifeMC/tree/main

[Nukecraft5419]

Basically if you didn't understand, I wanted to know if the way I did it is okay so it does the pulls and the various things that the classic method does but with improvements i.e. branch apart "l10n_main" where it does the various changes with the commits divided by language I think that was the classic method like en_gb (English UK) and so on and then it does a PR where it sends everything to the main I don't know if that's how I did it

[andrii-bodnar]

@Nukecraft5419 I don't see the corresponding changes in your repo. Just set up the GH Action in a separate branch and then I will see if it's ok. I need to see the GH Action run logs as well

[Nukecraft5419]

Perfect I will send the change as soon as possible in the dev_main branch

[Nukecraft5419]

I sent the commit but nothing started
https://github.com/LifeMC-Studios/LifeMC/blob/dev_main/.github/workflows/crowdin-sync.yml

[andrii-bodnar]

@Nukecraft5419 It's because your action trigger is set up for the main branch.

Please refer to the:

• OAuth to Actions migration guide
• Learn GitHub Actions
• Events that trigger workflows
• Encrypted secrets

[Nukecraft5419]

I see then I send the PR to the main so the whole thing starts

[andrii-bodnar]

@Nukecraft5419 the workflow is correct

[Nukecraft5419]

So I can send that modification and it should solve everything for me right?

[andrii-bodnar]

@Nukecraft5419 now you can change the Action version back to v1. Based on the recent logs it's obvious that GitHub Actions are not allowed to create pull requests in your repository.

To allow this, go to the repo settings > Actions > General and select the "Allow GitHub Actions to create and approve pull requests" checkbox.

[Nukecraft5419]

It won't let me change it, then I noticed there is v1.12.0 even though I'm using the build you told me to use

[Nukecraft5419]

I solved it and why I had to do it first inside the organization settings and then in the repository even though it gets them from there, now what version I use of the bot