Technical Documentation
Return to Main Documentation
ENGLISH - version 2.2
ENGLISH - version 2.2
  • Introduction
  • Getting started
    • Create your fork
    • Configure your fork
    • Keep your fork updated
    • Communication
  • Installation
    • Local installation
      • Prerequisites
      • Ubuntu Linux
      • Debian Linux
      • macOS
      • Windows
      • Vagrant
      • Docker
    • Production and staging servers
      • Installer
      • Create a deploy user
      • Generating SSH Key
      • Manual installation (not recommended)
      • Digital Ocean
      • Heroku
      • Mail server configuration
    • Basic configuration
    • User documentation and guides
  • Customization
    • Introduction
    • Translations and texts
    • Images
    • Styles with CSS
    • JavaScript
    • Models
    • Controllers
    • Views and HTML
    • Components
    • Other Ruby classes (GraphQL, lib, mailers, builders)
    • Gems
    • Application configuration
    • Routes
    • Tests
  • Technical Features
    • OAuth
    • GraphQL
    • Debates and proposals recommendations
    • Configure Census Connection
    • Local Census
    • Multitenancy
    • User content translations
  • Open Source project
    • Code of conduct
    • Contributing
    • License
    • Open source forks and modifications
Powered by GitBook
On this page
  • Continuous Integration with GitHub Actions
  • Steps to enable GitHub Actions
  1. Getting started

Configure your fork

PreviousCreate your forkNextKeep your fork updated

Last updated 8 months ago

Continuous Integration with GitHub Actions

is a tool integrated into GitHub that allows you to automate tasks such as running tests every time you make a change to your code. Since Consul Democracy already includes predefined configurations for GitHub Actions, enabling continuous integration in your fork is very straightforward.

Steps to enable GitHub Actions

  1. Enable GitHub Actions in your fork:

    1. Once you have created the fork, go to the "Actions" tab in your GitHub repository.

    2. You will see a message that says: "Workflows aren’t being run on this forked repository." This is normal because GitHub disables workflows by default in newly forked repositories for security reasons.

    3. Click the "I understand my workflows, go ahead and enable them" button to enable workflows in your fork.

  2. Verify the configuration:

    1. Make a change to any project file (for example, edit a .md file) in a branch other than master and push it to your fork.

    2. Open a pull request from the new branch to master in your fork.

    3. Go to the "Actions" tab and verify that the tests are running correctly based on the workflows defined in the project's .github/workflows/ directory.

GitHub Actions