Quira Docs
  • πŸ“ƒQuira docs
  • For Developers
    • πŸ› οΈGetting set up
      • 1️⃣Sign up with GitHub
      • 2️⃣Verify your email
      • 3️⃣Set up your profile
      • βš™οΈAccount management
    • Creator Quests
      • Creator Quests standard rules
    • Solver Quests
      • πŸ‘Public Solver Quests
      • πŸ”Private Solver Quests
    • πŸ’ΈClaiming rewards
  • For Organisations
    • πŸ› οΈGetting set up
    • Creator Quests
    • Solver Quests
      • Public Solver Quests
      • Configuring Solver Quests
      • Abort or edit a quest
      • Common errors with @quest-bot
  • Get in touch
    • πŸ“žContact us
Powered by GitBook
On this page
  • Editing a Quest
  • Aborting a Quest
  1. For Organisations
  2. Solver Quests

Abort or edit a quest

Editing a Quest

In some scenarios you may want to change the value of a reward after a Quest has already started (i.e. after the Quest has originally been 'stashed').

This can be achieved using the restash command in the target Issue, specifying a new reward_value to provide an updated value for the Quest:

@quest-bot restash {reward_value}

If this is successful you will see a message like:

The loot on Quest #{issue_number} has been restashed by @{organisation}.

πŸ’°Β The loot available is now ${new_reward_value}.

Aborting a Quest

In some situations, you might want to abort a Quest. This action is not recommended if some time have passed since the start of the quest because if a Quest has already started, the work of some developers may go unrewarded.

To abort a Quest call the abort command on the Issue where the Quest was initialised. The Issue number #{issue_number} must be included for added security:

@quest-bot abort #{issue_number}

A confirmation message like this will appear in the Issue. Developers who have called embark on the Quest will be notified:

Swords down πŸ—‘

Quest on issue #{issue_number} has been aborted by @{organisation}

...

Quests can also be aborted directly from the Admin Dashboard using the Manage Quest menu on the appropriate Quest page, or by simply closing the issue on Github.

PreviousConfiguring Solver QuestsNextCommon errors with @quest-bot

Last updated 1 month ago