Disable add file option in github

[white spoke]

Good day everyone. Please how can I disable the ability to add a file from github without using git commands. I want to be able to use git commands only.

[sick jetty]

Will power 😆

Don't use that option.

[white spoke]

Lol🤣

Am actually asking because I recently created a collaboration project and I dont want my collaborators to use that option, so I want to know how to block it.

Or what access is best for that. If I give them write access, the option will be availiable but if I give them a triage access it will not but I dont know if they will be able to push to the repo with that triage access

@sick jetty please how can this be done?

@merry crane I also need your help with this please

[sick jetty]

Any particular reason why you want to force them to use CLI?

Developer experience through code editors, dev tools like CLI etc should very much be customised to the developer's comfort level and understanding. You, as project lead could enforce some etiquettes in the code but should really not enforce ways to stop them or cause hurdle in the way they want to code and collaborate.

[white spoke]

If they dont use CLI there can easily be errors in the codes. I want them to be able to create a new branch and then create pull requests instead of pushing directly to main brach. Becase the add file option adds the code directly to main.

I dont know if you git?

[white spoke]

Very true. But am scared of having losing really important codes that takes time. Because it has actually happened to me before.

[sick jetty]

You can protect main branch and force that from being merged.
You can setup CI/CD so that after pushing their code will be auto checked using github actions or some other tool that will ask them to fix those changes , until those are fixed the PR is not considered valid.

Look into this https://codeclimate.com/quality

[white spoke]

This sounds cool and better.

[sick jetty]

And about protected branches https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches

[white spoke]

Thanks alot @sick jetty . I will look into them and give my feedback later.

[sick jetty]

the goal is to let them code and do the intended work and then fix the minor changes like spaces/tabs/semicolons/ etc

[white spoke]

Very true. Thanks againg sir.

[sick jetty]

There also husky which many big projects use https://github.com/typicode/husky but this can be overdone with pre commit rules. Either way its a popular tool used to maintain code quality and repo quality.