Skip to content

Latest commit

 

History

History
40 lines (26 loc) · 3.06 KB

PRT.md

File metadata and controls

40 lines (26 loc) · 3.06 KB
Raw

you can also see the tutorial from senpai there (part of it is basicaly same as that tutorial).

  • first, at Gideon9212/Livecustom, click the buttom fork

step 1.a

  • it will leave you with the result bellow (of with you github acount name).

step 1.b

  • they as above you can see 3 option, "create new file","upload new file","find file", first let upload the cdb, click on "upload a new file"

step 2.a

  • upload you cdb (give it a name like youname.cdb), and click at commit changes.
  • since you probaly going to upload more than 1 file, leave option at Commit directly to the master branch.
  • you can put a description and a commit name there or leave it in that state, it depend on where you will upload.
  • once you done you will back to bellow page.

step 2.b

  • it will have the file you uploaded, but you still need to upload script and cdb, just click on each folder and upload respectives archive.
  • remind script may be named c[id here].lua (ex: id = 210000000 so it script file will be c2100000000.lua)
  • remind pics are in jpg (or png if game suport it) with preferably 177 x 254 pixels, and it name is made similia way as script, except it is [id].jpg (in same case of example, 210000000.jpg)
  • once you upload both script and pic, click the "create pull request buttom"

step 3

  • the first mean where you uplading the changes and segond is from where you getting these changes, before clicking Create Pull Request, check if the first is the correct repository you want to upload and if all files are in that pull request.
  • once you click it, it will apear a space where you insert tittle and a description of PR, give the PR a good and informative name, and if you want to put details about it, do it in comments.
  • once you done click create PR, they you will have that screen.

step 4

  • if the name don't match, it probaly mean you done Pr in wrong repository.
  • if it match (gideon/livecustom), just wait for gideon to review it and give final word.

observations:

  • case you branch is not even with the branch you forking, there a small probability that the PR (Pull Request) got some conflict (so it can't be merged), in case you want to be sure to avoid that, you can simply refork, by deleting the current fork on forked reporistory, settings>delet this repository, they fork again (don't doo this if you still have a open PR as it will close it without merging).
  • having a PR open don't mean you can't change the changes, just click fork again and back to repository used for PR, and do the additional changes you want.