238d02f82c
* Make changes for multiple config files * Clarify deprecated procedure * Optimize images * More WiP changes * More WiP changes * Update s/shots - no longer beta * Optimize images * More WiP changes * Fix broken links * WiP * Add authorizations screenshots * Optimize images * Reorg requested by reviewer * Update content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md * Update content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md * Update content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md * Update content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md Co-authored-by: Felicity Chapman <felicitymay@github.com> * Update content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md * Update content/codespaces/troubleshooting/troubleshooting-prebuilds.md Co-authored-by: Felicity Chapman <felicitymay@github.com> * Update data/reusables/codespaces/billing-for-prebuilds.md * Tiny tweak to creation article * Another tiny tweak to creation article * Fix self-referential link Co-authored-by: github-actions <github-actions@github.com> Co-authored-by: Felicity Chapman <felicitymay@github.com>
879 B
By default, a {% data variables.product.prodname_actions %} workflow is triggered every time you create or update a prebuild template, or push to a prebuild-enabled branch. As with other workflows, while prebuild workflows are running they will either consume some of the Actions minutes included with your account, if you have any, or they will incur charges for Actions minutes. For more information about pricing for Actions minutes, see "About billing for {% data variables.product.prodname_actions %}."
Alongside {% data variables.product.prodname_actions %} minutes, you will also be billed for the storage of prebuild templates associated with each prebuild configuration for a given repository and region. Storage of prebuild templates is billed at the same rate as storage of codespaces.