# "Aucun réglage nommé \_\_ n'existe" en essayant d'exécuter des spécifications sur le plugin de sondage

**URL:** <https://meta.discourse.org/t/no-setting-named-exists-when-trying-to-run-specs-on-poll-plugin/199751>\
**Category:** Product Support\
**Created:** [Août 8, 2021, 11:36 UTC](https://meta.discourse.org/t/no-setting-named-exists-when-trying-to-run-specs-on-poll-plugin/199751 "2021-08-08T23:36:39Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [Septembre 27, 2022, 6:24 UTC](https://meta.discourse.org/t/no-setting-named-exists-when-trying-to-run-specs-on-poll-plugin/199751/11 "2022-09-27T18:24:38Z")

</div>

> [@david](#):
>
> Je soupçonne que, pour que cron fonctionne, nous devrons remplacer toutes les occurrences de `github.event.repository.name` par autre chose :

@cvx vient de partager cet article avec moi :

> **[GitHub Actions: Additional information available in github.event payload for...](https://github.blog/changelog/2022-09-27-github-actions-additional-information-available-in-github-event-payload-for-scheduled-workflow-runs/)**
>
> Additional information has been added to the payload of github.event for scheduled runs. Before this change, github.event for scheduled runs would only include the cron schedule. This change adds information…

Le contournement «&nbsp;hacky&nbsp;» du nom du dépôt ne devrait donc plus être nécessaire pour les tâches cron :tada&nbsp;: cc @merefield

---

_[View the full topic](https://meta.discourse.org/t/no-setting-named-exists-when-trying-to-run-specs-on-poll-plugin/199751)._