Migrate from GitHub Macros for Confluence
You can migrate from the GitHub Macros for Confluence app (by Appfire) to Capable Git.
#GitHub File
The Appfire GitHub File macro is migrated to Capable Git.
#What the migrator does
Reads the file path, repository, user, and branch from macro parameters
Constructs the full GitHub file reference for the Capable Git macro
Converts the macro to a Capable Git macro with the equivalent configuration
#Support level
Partial — Basic GitHub file embedding is migrated. Line range filtering is not supported — if the original macro was configured to show only specific lines of a file, the migrated version will display the entire file.
Follow the instructions on Using the migration assistant to run the migrator.
#GitHub Markdown
The Appfire GitHub Markdown macro is migrated to Capable Git.
#What the migrator does
Converts GitHub markdown file references to the Capable Git macro format
Renders the markdown content from the referenced file
#Support level
Partial — Markdown file references are migrated. Authentication tokens are not migrated — if the original macro used a personal access token to access a private repository, the user will need to re-authenticate through Capable's per-user GitHub authentication.
Follow the instructions on Using the migration assistant to run the migrator.
#Unsupported macros
The following Appfire GitHub macros are detected but cannot be migrated at this time. They will appear in the migration assistant with page counts for visibility:
Macro | Key | Notes |
|---|---|---|
GitHub Issue List |
| Issue tracking not available in Capable |
GitHub Pull Request List |
| PR tracking not available in Capable |