# Impossible to share my step : "No step collection specified"

**URL:** https://discuss.bitrise.io/t/impossible-to-share-my-step-no-step-collection-specified/4002
**Category:** Step Dev
**Created:** [February 2, 2018, 1:04pm UTC](https://discuss.bitrise.io/t/impossible-to-share-my-step-no-step-collection-specified/4002 "2018-02-02T13:04:22Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![kawaiseb](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/kawaiseb/32/893_2.png) [@kawaiseb](https://discuss.bitrise.io/u/kawaiseb)
#### Post date: [February 2, 2018, 1:04pm UTC](https://discuss.bitrise.io/t/impossible-to-share-my-step-no-step-collection-specified/4002/1 "2018-02-02T13:04:22Z")

</div>

Hi bitrise team 🙂

I’am trying to share my first step… But when i’m running :

> bitrise run share-this-step

I have got the following message :

> FATA[13:47:08] No step collection specified

I don’t exactly what it means…  
My step is here for information : [https://github.com/kawaiseb/bitrise-step-wetransfer-upload/blob/master/bitrise.yml](https://github.com/kawaiseb/bitrise-step-wetransfer-upload/blob/master/bitrise.yml)

Thanks for your help.

---

<div class="post-metadata">

### Author: ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)
#### Post date: [February 2, 2018, 1:31pm UTC](https://discuss.bitrise.io/t/impossible-to-share-my-step-no-step-collection-specified/4002/2 "2018-02-02T13:31:14Z")

</div>

Set this env (`MY_STEPLIB_REPO_FORK_GIT_URL`) [https://github.com/kawaiseb/bitrise-step-wetransfer-upload/blob/master/bitrise.yml#L27](https://github.com/kawaiseb/bitrise-step-wetransfer-upload/blob/master/bitrise.yml#L27) e.g. in secrets, then run again the `bitrise run share-this-step` workflow, that should work 😉

P.S.: the `MY_STEPLIB_REPO_FORK_GIT_URL` have to be a fork of the step lib you want to share your step into, most likely into our primary one, in that case just fork [https://github.com/bitrise-io/bitrise-steplib](https://github.com/bitrise-io/bitrise-steplib) and set your fork’s git clone url.

If you’d have any questions just let us know! 🙂

---

<div class="post-metadata">

### Author: ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)
#### Post date: [February 2, 2018, 1:33pm UTC](https://discuss.bitrise.io/t/impossible-to-share-my-step-no-step-collection-specified/4002/3 "2018-02-02T13:33:27Z")

</div>

Actually you can find even more details in the workflow’s description: [https://github.com/kawaiseb/bitrise-step-wetransfer-upload/blob/master/bitrise.yml#L90](https://github.com/kawaiseb/bitrise-step-wetransfer-upload/blob/master/bitrise.yml#L90)

But of course if you’d have any questions just let us know! 😉

---

<div class="post-metadata">

### Author: ![kawaiseb](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/kawaiseb/32/893_2.png) [@kawaiseb](https://discuss.bitrise.io/u/kawaiseb)
#### Post date: [February 2, 2018, 5:28pm UTC](https://discuss.bitrise.io/t/impossible-to-share-my-step-no-step-collection-specified/4002/4 "2018-02-02T17:28:57Z")

</div>

Thanks Viktor ☀  
I forked the steplib project , changing my version etc. and made my PR 🙂  
Everything seems ok. Now it’s up to you eheh. Be nice with me.

---

<div class="post-metadata">

### Author: ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)
#### Post date: [February 3, 2018, 12:57pm UTC](https://discuss.bitrise.io/t/impossible-to-share-my-step-no-step-collection-specified/4002/5 "2018-02-03T12:57:23Z")

</div>

> [@kawaiseb](#):
>
> I forked the steplib project , changing my version etc. and made my PR 🙂

Glad to hear! 🙂

> [@kawaiseb](#):
>
> Now it’s up to you eheh. Be nice with me.

Don’t worry, we will 😃

P.S.: as this is a completely new step we’ll do a more thorough check on it, so it might take some time to accept it; subsequent step updates will be significantly faster 😉
