# Different resource\_class for OSS forks

**URL:** <https://discuss.circleci.com/t/different-resource-class-for-oss-forks/46751>\
**Category:** Build Environment\
**Tags:** circle-yml, oss\
**Created:** [January 17, 2023, 9:06pm UTC](https://discuss.circleci.com/t/different-resource-class-for-oss-forks/46751 "2023-01-17T21:06:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cdhunt](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/cdhunt/32/29717_2.png) [@cdhunt](https://discuss.circleci.com/u/cdhunt)\
**Post date:** [January 17, 2023, 9:06pm UTC](https://discuss.circleci.com/t/different-resource-class-for-oss-forks/46751/1 "2023-01-17T21:06:28Z")

</div>

We have an [OSS project](https://github.com/StackExchange/dnscontrol/blob/master/.circleci/config.yml#L24) that is under our Scale plan, but if someone forks the project the build fails because they don’t have access to the `2xlarge` class.

Is there already a `config.yml` pattern for handling this? If you pass `resource_class` an empty string will it fall back to the default?

---

<div class="post-metadata">

**Author:** ![FelicianoTech](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/felicianotech/32/21348_2.png) [@FelicianoTech](https://discuss.circleci.com/u/FelicianoTech)\
**Post date:** [January 22, 2023, 12:06am UTC](https://discuss.circleci.com/t/different-resource-class-for-oss-forks/46751/2 "2023-01-22T00:06:08Z")

</div>

I love this idea and I don’t think we have a solution for this now (I could be wrong). I would suggest adding this to [https://ideas.circleci.com](https://ideas.circleci.com)