Does anyone know the current status of the BWS?

[AL|EN]

ell, I place my bets on "Permission denied (publickey)" Did you forked BWS using BitBucket "Fork" website button? How those settings look at you SmartGit: https://image.prntscr.com/image/330c1024ee2c41a898c9bbd56cfc8d60.png ? I can help you but I need to know exactly what you did and what git authentication method did you use.

[Roxanne]

ell, I place my bets on "Permission denied (publickey)" Did you forked BWS using BitBucket "Fork" website button? How those settings look at you SmartGit: https://image.prntscr.com/image/330c1024ee2c41a898c9bbd56cfc8d60.png ? I can help you but I need to know exactly what you did and what git authentication method did you use.

Honestly, I tried various ways I know and deleted my local copy now several times. I went from my SmartGit tool as well as an attempt with the Fork button selecting Smartgit as program to use.

I have the settings as shown in your picture.

[AL|EN]

I've made a lite video for you: http://webm.land/media/UiV3.webm (chrome/Firefox) Please follow this steps, correct my mistake and at the end, hit "Push" button and post errors if they popup.

[Roxanne]

I've made a lite video for you: http://webm.land/media/UiV3.webm (chrome/Firefox) Please follow this steps, correct my mistake and at the end, hit "Push" button and post errors if they popup.

Everything like in your video - only, at the point (0:11 sec) an option is missing

 

And when selecting push

It asks me for authorisation - I ask for token method and follow it.

Result

 

I also used in a previous attempt password method with my bitbucket account but it has the same issues.

 

It is only for BWS repository - I can push to github and bitbucket to my own accounts and groups.

[AL|EN]

It's probably the difference between version as I'm using 17.1 preview 8. As for authentication errors: you cannot push directly to BWS repository unless you are added as project maintainer. You have to create "Pull Request" from you remote fork into original BWS repository:

- go to you own remote repository using web interface ( at the list of commits, you should see you last commit message "Corrected SoDBanters ..."

- hit Create pull request button, theoretical example: https://image.prntscr.com/image/7616bc1db8b44f35827ca7be3b215208.png

- at the next screen, you should see roxanne/bigworldsetup on the left side and "bigworldsetup/bigworldsetup" at the right side

- leave branches as "master", write short description or copy commit message

- hit Create pull request button again

 

I shall get notification and I can include changes from you remote repo into main BWS repo using single click.

[Roxanne]

It's probably the difference between version as I'm using 17.1 preview 8. As for authentication errors: you cannot push directly to BWS repository unless you are added as project maintainer. You have to create "Pull Request" from you remote fork into original BWS repository:

 

>>>>> I was expecting something like that

 

- go to you own remote repository using web interface

 

>>>>> All I see is my own test repository, nothing else which resembles your description at all. Maybe all is different for the owner? I can see others like jastey branch but nothing for RoxanneSHS.

 

( at the list of commits, you should see you last commit message "Corrected SoDBanters ..."

- hit Create pull request button, theoretical example: https://image.prntscr.com/image/7616bc1db8b44f35827ca7be3b215208.png

- at the next screen, you should see roxanne/bigworldsetup on the left side and "bigworldsetup/bigworldsetup" at the right side

- leave branches as "master", write short description or copy commit message

- hit Create pull request button again

 

I shall get notification and I can include changes from you remote repo into main BWS repo using single click.

Nothing seems to match in your view and mine, see above inserts.

[AL|EN]

Gon't give up yet

0. remove you 'bwsclone' remote repo to not confuse you at the time when you will use interface (https://bitbucket.org/RoxanneSHS/bwsclone)

1. open https://bitbucket.org/BigWorldSetup/bigworldsetup

2. depending how you main page look, you have to find "Fork" button - Example 1 / Example 2

3. Click click this button, click "Fork" again, you should now have fork of bigworldsetup repository - you should have something like https://bitbucket.org/RoxanneSHS/bigworldsetup

4. Using SmartGit, clone this forked repository to you local PC. You have to choose this new fork, not the repo which you created by yourself

5. Make the same changes/fixes to the files which you done for you bwscloone repository

6. commit it again to you local bigworldsetup repo

7. Push it to you remote fork of bigworldsetup, you should see you last commit at the web interface -> commits

 

Let's stop here until we will at the same step.

[Roxanne]

Gon't give up yet

0. remove you 'bwsclone' remote repo to not confuse you at the time when you will use interface (https://bitbucket.org/RoxanneSHS/bwsclone)

1. open https://bitbucket.org/BigWorldSetup/bigworldsetup

2. depending how you main page look, you have to find "Fork" button - Example 1 / Example 2

3. Click click this button, click "Fork" again, you should now have fork of bigworldsetup repository - you should have something like https://bitbucket.org/RoxanneSHS/bigworldsetup

4. Using SmartGit, clone this forked repository to you local PC. You have to choose this new fork, not the repo which you created by yourself

5. Make the same changes/fixes to the files which you done for you bwscloone repository

6. commit it again to you local bigworldsetup repo

7. Push it to you remote fork of bigworldsetup, you should see you last commit at the web interface -> commits

 

Let's stop here until we will at the same step.

Done. I am so embarrassed I was not able to manage that - I was searching for hours for that *fork* button in your step 2. In my screen it was hidden in a section that needed expanding. After that...all smooth.

 

So my first attempt should now be at point 7. I can see the changes in my fork on the web.

[AL|EN]

Great! Now' let's put you fix into BWS:

 

0. Open https://bitbucket.org/RoxanneSHS/bigworldsetup/pull-requests/

1. There should be a create a pull request. link or bigger, blue Create pull request button at the top right.

2. You should get something like this but with you repository/fork details at the left side: http://i.imgur.com/YGG2CuL.png , leave everything as default

3. Click Create pull request button and viola, I should get a proposition to include you changes into BWS.

[Roxanne]

Great! Now' let's put you fix into BWS:

 

0. Open https://bitbucket.org/RoxanneSHS/bigworldsetup/pull-requests/

1. There should be a create a pull request. link or bigger, blue Create pull request button at the top right.

2. You should get something like this but with you repository/fork details at the left side: http://i.imgur.com/YGG2CuL.png , leave everything as default

3. Click Create pull request button and viola, I should get a proposition to include you changes into BWS.

Done.

Thank you for your patience with me.

It is really that bitbucket interface, terrible. I got accustomed to Github which is truely intuitive, this one is a nightmare. (I need something to shift the blame to, I cannot admit my own faults...).

[AL|EN]

Yee, GitHub owns, but there is one important problem: when you download master branch, you don't get the commit id for you filename - I've requested this feature 2 ears ago. It allows to know exactly which BWS version the user has when they reporting bugs.

 

Anyway, I've posted two comments regarding smal mistakes, please correct them, comit and push them. Because they are on master branch, there is no need to create yet another PR for every change until i finally accept/merge this PR.

[lynx]

Actually, the HEAD commit hash is stored in the master.zip metadata (zip comment). Ark displays it for me and it is also visible to unzip. Eg., with IESDP:

https://github.com/Gibberlings3/iesdp Latest commit 35721c5 25 days ago

$ unzip -l iesdp-master.zip | head -n2
Archive: iesdp-master.zip
35721c55b016c7cdc1ab00e954be5424e051bf13

 

If this is hard to do on windows for some reason, there are other ways of finding out / storing the hash.

[AL|EN]

@RoxanneSHS And we are done: https://bitbucket.org/BigWorldSetup/bigworldsetup/commits/17e370f6d68e943891fa47a4ed695fc666144583

 

Merged in RoxanneSHS/bigworldsetup (pull request #46) Added Thief Stronghold for EET Corrected SoD Banter Mod entries

 

@lynx I didn't know that there is such information inside metadata, no one from github staff mention about it. Still, it's not a matter of OS and tools, it's a matter of hosting. BitBucket include such information inside filename, github not - this simple difference lead to avoid repeting scenario when you have to tell user to run some comandline in order to get commit id/version of the BWS.

[lynx]

Well no, it can be saved elsewhere and displayed in BWS. Or if you tell users to use a different URL to download BWS, it would be simple to add an intermediary service to grab master.zip and rename it to, let's say, master-$hash.zip.

[subtledoctor]

I can't pretend to understand most of what is being discussed here. Are you guys keeping BWS up-to-date?

 

If so, if it matters, one of my mods has a slight chance in the install order. Might & guile component #500, formerly the last component, should now be installed first, before component 200.

 

I have not changed the DESIGNATED numbers, for fear of messing up BWS; I've only moved the last component to the front of the mod. And honestly it doesn't make much difference at all, so if it's problematic to effect this change in BWS, then just ignore this post.