이제 로컬 복제본을 가져야 합니다. 변경하려면 먼저 Mercurial/Git 클라이언트의 올바른 브랜치로 이동하여 소스 코드의 올바른 버전에 액세스해야 합니다. 그런 다음, 수정할 수 있습니다.
이 예제에서, Unity Test Tools 저장소는 새로운 것이고 안정된 브랜치에 대해 하나의 커밋만 있습니다. 다음은 해당 버전을 명시적으로 업데이트하는 예제입니다.
올바른 버전의 소스 코드가 있으면 수정한 내용을 수정할 수 있습니다. Mercurial/Git 클라이언트로 돌아가면 파일을 수정했음을 감지합니다.
수정된 파일은 Working Copy 뷰에서 확인할 수 있습니다. __Commit__을 클릭하여 변경 사항을 반영해야 합니다.
그런 다음, 변경 사항을 누릅니다. 클라이언트는 푸시되기를 기다리는 변경 집합의 수를 표시합니다.
Push 를 클릭하여 변경 사항을 푸시해야 합니다.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.