Page Comparison

...

Expand

title	STEP 2: Commit some code changes and push them to the remote repository

Now that there is a git repository tracking this component, changes made locally can be committed and saved to the cloud.

Click on Edit Script to open the Translator
Make some code changes. If nothing comes to mind, replace the code you see with the sample below, Now change the code to the following which just changes the component’s border on the dashboard to red
Code Block
language lua
function main() component.setBorder{color="red"} end main()
Once you have made some changes, click on the Commit Changes button in the Translator toolbar, its the one that looks like a plus surrounded by a circle
In the window that appears you can see the changes that were made. Enter a message that summarizes the changes, then click Commit
You will be sent back to the Translator screen. Notice that there are a few changes:
- The Push Changes button in the Translator toolbar which looks an arrow pointing to a cloud has a blue dot. This means a local change is ready to be pushed to the cloud repository.
- A new section has appeared at the bottom. This is the Git Terminal. This is where you will see information appear when Git commands like pulling, committing and pushing are done.
- Users familiar with how Git works can use this terminal to perform Git operations.
Click on the Push Changes button. If Git was able to successfully send your changes to the remote repository, you will see this:
Now your changes are on the remote repository, they are ready to be imported in to any other Iguana instances you have
Exit Translator by hitting the X in the top right

Expand

title	STEP 3: See the local code change in effect

The code change from the previous step was committed to the remote repository, but the component is not yet using the new code. The component must updated to use the new commit.

In the component card, use the Using Commit dropdown and change the commit the component is running on to the commit you made.
Image Added
Now close the card and run the component. You should see it get a red outline
Image Added

Expand

title	STEP 4: Clone in your component on a different Iguana and update the code

Since the changes made have been pushed to the cloud, this component can now be cloned into any other Iguana.

Exit the Translator by clicking the X in the top right

Note: To try out this step you need to have a different Iguana instance ready with Bitbucket access configured. See: Setting up Bitbucket Access

Open the component that was created. From the component card, copy the Connected To field
In a different Iguana instance, from the dashboard click + From Url. Give the component a name, and paste in the url from before
Image Removed
then click Add
Image Added
Once the component is created, click Edit Script to go to Translator
- You may have to click and expand the Implementation section
See that the code changes made in the previous step have been brought across
Change to the code to the following, then commit and push the change.
Code Block
function main() component.setBorder{color="green"} end main()
Back on your other Iguana instance, update the component to run from this new commit. It can take a minute or two for the new commits to show up.
- Use the Using Commit dropdown and select the commit you just made
  Image Added
Now run the component and verify that the border turns green
Image Added
Click on Edit Script to go to the Translator. To see the code changes, we have to pull in the changes from the remote repository.
- Do this by clicking on the Pull Changes button which looks like a cloud with an arrow pointing away from it.
- Notice that it has a blue dot, indicating that there are changes available to be pulled in. Click it and see that the code updates.
  Image Added

Expand

title	STEP 5: Add this component to a collection

[This feature has some issues in 10.1.70]

Versions Compared

Old Version 7

New Version 8

Key