DEVOPS, github, gitea, jenkins CI/CD

a newly installed gitea instance on a server. It is not a docker instance...

Short description and what to do:
a newly installed gitea instance on a server. It is not a docker instance...

1. We need help with merging, squashing code in gitea as it says
wont sign: nokey
I have added keys in the SSH/GPG tab. This is happening specifically with one account from a windows machine.

2. The windows machine can generate and verify the SSH/GPG key from the command prompt and from github app in windows and he can also add the key to gitea. but when it is verified in gitea it does not work to verify it.

3. when I pull from gitea there is a password that never resolves and I cannot pull code to the server to manually merge and push back to gitea. I need to clone the code and cannot just do git remote add origin XXXXX.

4. When developers wants to get a copy of the code they will have read rights. One developer tried to upp from one of the repositories. He only got a password request. How do we do it so they do not need to verify their keys every time?

5. jenkins and gitea is already up and running.


Scripts in jenkins/Gitea that must be run:

1. Branches: feature/bug/change branches, MASTER.
When the magento developer push code he push to master currently because all errors in the purchased modules. We should run tests in our own module only, …/app/code/XXXXX/* .there are some other branches also I will add, it is one or two more.
The gitea/Jenkins should push the code according to the example in the URL I have pasted below.
How it should work:
a. Actions: test magento code,
b. Create Pull Request: run tests
c. Admin code review: Mandatory OR autmaitcailly on each branch they create (follow example in the URL)
d. When Admin approve: merge, then allow merge or squashing.
e. When Merging: merge manually into develop, compile the code from develop
f. Releases to master: Manually, compiling and testing if there are any tests
g. Scripts: exists in github already. The compilation is now on the branch but it should be on the develop branch only.
- Linter tests should be run
- Code standard should be run (like in Magento)

h. General:
This is the scenario how it should work: https://www.madit.fr/blog/our-blog-1/post/zero-downtime-deployment-magento-6

2. Branches: feature/bug/change branches,
a. Actions: test flutter code,
b. Create Pull Request: run tests
c. Admin code review: Mandatory on each branch they create.
d. When Admin approve: merge, then allow merge or squasging.
e. When Merging: merge manually into develop, compile the code from develop
f. Releases to master: Manually, compiling and testing if there are any tests
g. Scripts: exists in github already. The compilation is now on the branch but it should be on the develop branch only.
- Linter tests should be run
- Code standard should be run (like in Magento)

h. General: Most tests are just for linter which seems to clean up a lot of rubbish.
Some link example for tests: https://swerdlowben.medium.com/automating-flutter-testing-with-github-actions-f3a986596794

3. Wait with this until last thing: feature/bug/change branches, test native AND mediapipe code, merge into develop, compile, then create releases to master I have scripts code for native, flutter and magento.

I have scripts code for native, flutter and magento.

Qualifying question you must answer:
- have you set up and used gitea on a ssh instance (not docker)?
- have you resolved key problems in gitea?
- have you setup jenkins/drone and drone runner in gitea to run scripts?

Your skills:
- gitea experience, yes, searching on the web is something I can do too so you must have true experience.
- jenkins/drone
- jenkins/drone runner experience
- setup scripts imported from github to run on gitea
- install so gitea can compile automatically when pushing code to feature branches.

Please note, you MUST have gitea experiences. I am not interested in someone who can read and search the internet. And yes, I can see and understand I you have no skills in gitea when I see you working.
I do not want to waste time on a person who has no experience.