Follow the instructions below to gain editing access to Citrix GitHub documentation repositories
Something went wrong opening the GitHub link. Please try again.
Last published : Sep 03, 2026
You might want to force a failover if, for example, you need to replace or upgrade the primary node. You can force failover from either the primary or the secondary node. A forced failover is not propagated or synchronized. To view the synchronization status after a forced failover, you can view the status of the node.
A forced failover fails in any of the following circumstances:
You force failover on a standalone system.
The secondary node is disabled.
The secondary node is configured to remain secondary.
The NetScaler Gateway appliance displays a warning message if it detects a potential issue when you run the force failover command. The message includes the information that triggered the warning and requests confirmation before proceeding.
Follow the instructions below to gain editing access to Citrix GitHub documentation repositories
Step 1
Commit Guidelines
Before we start looking at the specific use cases, here’s a quick note about commit messages. Having a good guideline for creating commits and sticking to it makes working with Git and collaborating with others a lot easier. The Git project provides a document that lays out a number of good tips for creating commits from which to submit patches — you can read it in the Git source code in the Documentation/SubmittingPatches file.
Step 2
Private Small Team
The simplest setup you’re likely to encounter is a private project with one or two other developers. “Private,” in this context, means closed-source — not accessible to the outside world. You and the other developers all have push access to the repository.
Something went wrong opening the GitHub link. Please try again.