Available translations

App Contribute Command

foundations.png
Summary: This command allows you to contribute work to the project. The contribution goes to the Superalgos repository via a Pull Request from your Superalgos fork.
This command will send all changes you have made in Docs pages but also on any file within the Superalgos folder (except for My-Workspaces, Data-Storage, and My-Logs folders) to your fork at Github.com. It will also send them from your fork to the main Superalgos Repository. It will do it specifically from the Current Branch to the Contributions Branch mentioned at the footer of this page.
Master is our stable branch and it is very unlikely that we are going to merge contributions there. Instead, all contributions are expected to go to the develop branch, where many users are testing that branch every day. Contributions to the develop branch will reach the master branch on the next release.
Syntax
 app.contribute [Message]
Parameters
  • Message: Enter a brief description of what your contribution is about. It is optional but appreciated.
Example
 app.contribute Fixed typo.
For Devs
This is what the command does:
  • git.add: adds the changes you've made to contributable files to a git commit.
  • git.commit: commits all the changes.
  • git.push: pushes the changes to your fork.
  • github.createPullRequest: creates a Pull Request at the Superalgos repository, or add commits to an existing Pull Request.
Block Authentication
Authentication
For the App Contribute Command to run properly, two different authentications are required:
  • Git Authentication: The first time you run this command, Git will open a pop up window that will ask you for your Github.com credentials. This happens only once. Git will use these credentials to push the commit to your Superalgos fork at Github.com.
  • Github.com Authentication: The creation of the Pull Request is something that happens at Github.com and for this operation you need to authenticate too. To do this, you must generate a Personal Access Token and set it up at the Github Api node configuration in your active workspace.
GitHub.com Token
  • Create the token by following this link:
Github API Node
Once you have your token, find the GitHub API node (you may search for it in the Documentation). The configuration looks like this:
 {
    "username": "",
    "token": ""
}
If you can't find the node by using the search box, it may not exist in the active workspace. The APIs hierarchy is included by default in the Getting Started workspace only. You may spawn a new APIs hierarchy from the Other Hierarchies node in the Foundations Project hierarchy.
Properties
  • username: Type your GitHub.com username.
  • token: Paste the token you created.
Troubleshooting Authentication Issues
Some issues may arrise when you have more than one Git installation active in your OS.
For example, if you see the following authentication screen, it means an older version of Git is trying to deal with the authentication:
The current authentication screen is similar to this one instead:
Linux and macOS
If you don't want to keep entering in your token then you can have git cach your credentials:
Next
App Update Command

App Commands — TOC

You just read page 1 in the topic.

1. App Contribute Command

2. App Update Command