Unstable macos

[sotger]

Hi.
Unfortunately I don't know how to make pull request description.
This is my very first pull request with my folder in ././Content/OpenTournament/

[wail]

Hi Sotger,

Can you explain to me what you are trying to contribute to the project in this PR?

It's important that when you commit files to Git that you only include the files that you meant to change. This PR has 85 changed files, many of them do not seem to be ones you wanted to change, e.g.

• NavTestLevel.umap
• BP_Teleporter.uasset
• BP_CharacterSpawner.uasset
• BP_Player.uasset
• etc.

If you change many files unintentionally this can create bugs, so we need to ensure that your PR only has commits on the necessary files.

[sotger]

Hi Wail. I apologize if I did something wrong. I have some questions about working with GitHub and collaborating on the OT project. In this pull request, I added my folder with prototype levels and materials. Could you clarify the proper way to organize this? Should I create my own folders or use shared ones, like the “Levels” folder? How do other developers release their work, and how can I collaborate better, especially at the prototyping stage? This pull request doesn’t contain anything significant for the project—just maps and geometry. Since I’m not proficient in Blueprints or C++, I’d appreciate it if you could delete it. Thank you! P.S. If it’s not allowed to have my own working folder in the main repository, can I create my own branch (on my OT fork) to make pull requests to the main repository later? Will other files in my branch be automatically synchronized with the main branch, or will they remain in the state they were at the time of the snapshot? And how can I keep them up to date? сб, 14 дек. 2024 г. в 06:17, wail ***@***.***>:

…

Hi Sotger, Can you explain to me what you are trying to contribute to the project in this PR? It's important that when you commit files to Git that you only include the files that you meant to change. This PR has 85 changed files, many of them do not seem to be ones you wanted to change, e.g. - NavTestLevel.umap - BP_Teleporter.uasset - BP_CharacterSpawner.uasset - BP_Player.uasset - etc. If you change many files unintentionally this can create bugs, so we need to ensure that your PR only has commits on the necessary files. — Reply to this email directly, view it on GitHub <#365 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AATN5FKU6RT7WF25HJNHEXL2FOWMFAVCNFSM6AAAAABSLMZR36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBSHAYDGMJUGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Ответ на любой вопрос есть Любовь. +380674663494 Soundcloud <https://soundcloud.com/boris-kukoba/sets> Instagram <https://www.instagram.com/boriskukoba/> Facebook <http://www.facebook.com/kukoba>

[wail]

Hi Sotger

No worries, Git / GitHub can be challenging to learn.

Git / Submitting Files

1 important thing is to only commit files you changed intentionally. Sometimes when working in Unreal some files will be changed by accident, lets say I am creating a new map TestMapExample.umap By accident I might make a change to W_HUD_Master.uasset.
When I look in the GitHub client, I can see all changed files:

In this example it is important to uncheck any files you did not want to change before commit
You should also "Discard Changes" on files if you did not mean to change them.

File Organization

Recommendation:

Level Files (.umap) should be submitted in a subfolder: Content/OpenTournament/Levels/<YourMapName>/<YourMap>.umap

Other art assets:

• Materials: Content/OpenTournament/Materials/
• • You should create a new subfolder if you have many materials
• StaticMeshes: Content/OpenTournament/Meshes
• etc.