Home

Welcome to the Resurgo.AI Wiki!

If you're facing issues while using our repositories, such as outage-recovery-simulator-python, we've compiled troubleshooting tips to resolve the most common problems. If your issue isn't covered here, feel free to contact us or create an issue in the relevant repository, such as outage-recovery-simulator-python/issues.

---

Troubleshooting Tips

1. Actions Not Triggering After Pushing to main

Problem: You pushed or merged changes to the main branch, but the workflow described in the README.md didn’t run, and no Root Cause Analysis (RCA) was triggered.

Solution: Ensure GitHub Actions are enabled in your fork:

1. Navigate to the Actions tab in your repository.
2. Click the button: I understand my workflows, go ahead and enable them.
3. Reset your main branch to its original state and reapply your changes to trigger the workflow:

   git checkout main
   git reset --hard safe-spot    # Resets your local repository to the 'safe-spot' tag
   git push --force origin main  # Force-resets the remote main branch
   git rebase outage-db-configuration-error  # Reapply changes
   git push origin main

   Alternatively, delete your fork, fork the repository again, and enable GitHub Actions before merging changes into main.

---

2. Missing Outage Branches in Forked Repository

Problem: Your forked repository only contains the main branch, but you want to merge a pre-made outage branch (e.g., outage-db-configuration-error).

Solution: This happens if the "Copy the main branch only" option was selected during forking. To fix this:

1. Delete your current forked repository.
2. Fork the original repository again, ensuring you disable the "Copy the main branch only" option. This will include all pre-made outage branches in your fork.
3. Before merging changes into main, ensure GitHub Actions are enabled. See Actions Not Triggering After Pushing to main for guidance.