Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

RDK Central GitHub Components & its Product Branches

A list of the public repositories include:Please refer to this link to see all the repositories Source Code Repositories

ComponentProduct BranchLicenseDescription
RDKServicescurrent default branchApache
LightningmasterApache
Lightning-CLImasterApache
Lightning-SDKmasterApache
Lightning-UI-ComponentsmasterApache
OCDM-ClearkeymasterApache
OCDM-NagramasterApache
OCDM-PlayreadymasterApache
OCDM-WidevinemasterApache
RDKShellmasterApache
RDKSplashScreenmasterApache
ThundermasterApache
ThunderJSmasterApache
ThunderNanoServicesmasterApache
ThunderUImasterApache
DobbymasterApache
android-remotemasterApache
meta-turrismasterApache
opensync-vendor-rdk-turrismasterApache
rdkb-turris-halmasterApache
rdkcryptoapimasterApache
sample-licensingmasterApache

...

  • Create a Fork by simply clicking on the 'fork' button of the repository page on GitHub.
  • Clone your Fork, the clone command creates a local git repository from your remote fork on GitHub.
  • Modify the Code in your local clone, and commit the changes to your local clone using the git commit command.
  • Push your Changes by invoking the git push command, from your workspace, to upload your changes to your remote fork on GitHub.
  • Create a Pull Request by clicking the 'pull request' button on the GitHub page of your remote fork.

Configure your Github access token

In the recent past support for direct password authentication was removed from Github. You will need to generate a Github personal token to push your code changes RDK Central Github.

To create your personal token, you have to go to github.com -> Settings -> Developer Settings -> Personal Access Token -> Generate New Token.

Note - While creating a new token, it will ask for Github configuration options selection – Select everything.

Once the Github token is generated successfull, you will need to add an entry an entry to the ~/.netrc file OR you can directly use this token as your Github password in the command line to push the code changes.

Example: how to add Github credential on ~/.netrc file
machine github.com login your-github-handle-name password ghp_BCy09kNYxg82no6OnliSJQVngGi9K1234567

GitHub Protected Branches

...

Make the code changes, and commit the changes


cd Lightning-CLI
git checkout -b <branch-name> Note: give any name to your choice example JIRAID, CommitId, etc.

Modify your code.

$ git status
   Here You will see the files you have locally modified.
   
$ git add filenames
$ git commit -a 
   Add the following to your commit message.
        JIRA-ID Write a small description
        <One empty line>
        Reason for change:
        Test Procedure:
        Risks: 
        Signed-off-by:

$ git push -u (It will prompt you the right command to use for submitting your code changes)

After submitting your changes, follow the next step to create a PR.$ git add .
$ git status
$ git commit -m "<JIRA_TICKET_ID> <COMMIT_DESCRIPTION>"
$ git push


Step 4 : Create pull request for review the changes

...