Thanks for raising @dumbcoder7 👍 and sorry for the confusion.

Thanks @Vyvy-vi for replying. There is a fix for this now available by GitHub, I think we need to change the config a little bit to benefit from it

from hacktoberfest-practice.

I'm going to reopen this issue, cuz the issue still persists.

from hacktoberfest-practice.

It's great having you contribute to this project

If you would like to continue contributing to open source and would like to do it with an awesome inclusive community, you should join our Discord chat and our GitHub Organisation - we help and encourage each other to contribute to open source little and often 🤓 . Any questions let us know.

from hacktoberfest-practice.

Oh there's an open issue for this...
#342
#25
The workflow has a slight error. It doesn't work for forks, since they lack access to the repo's secrets
Don't worry about the statistics workflow failure 👍 as long as the build and lint workflow works(until the statistics workflow is configured)

from hacktoberfest-practice.

Okay, thanks.

from hacktoberfest-practice.

potential fix: https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#pull-request-events-for-forked-repositories

from hacktoberfest-practice.

@Vyvy-vi yes I think you are right 👍 . Let's try it 🤓

from hacktoberfest-practice.

thanks @adityaraute 👍

from hacktoberfest-practice.

Somebody please solve this. I am not skilled in this area sadly.

@Vyvy-vi did you try your fix, pal?

from hacktoberfest-practice.

I'll look into it 👍

from hacktoberfest-practice.

https://github.community/t/make-secrets-available-to-builds-of-forks/16166
https://github.community/t/allow-secrets-to-be-shared-with-forks-from-trusted-actions/16525

from hacktoberfest-practice.

Looks like a github issue

from hacktoberfest-practice.

But if GITHUB_TOKEN secret does not raise errors, why does this one do?

from hacktoberfest-practice.

FIREBASE_KEY

from hacktoberfest-practice.

The forked repo doesn't have the secret containing firebase key

from hacktoberfest-practice.

I think it would be best to not have the action run on forks, let me try a fix now

from hacktoberfest-practice.

Can you try to update your fork and now the GitHub Action should not run for the fork

from hacktoberfest-practice.

if this works, this condition should be added to all our community repos

from hacktoberfest-practice.

Do I just review a PR like I have did here?

from hacktoberfest-practice.

I reviewed a PR on this repo ( #297 ) error still persists.

from hacktoberfest-practice.

Was the fork updated with the latest code changes?

from hacktoberfest-practice.

Perhaps not. I am confused.

from hacktoberfest-practice.

We can see if anyone else reports it

from hacktoberfest-practice.

I think there was a second discussion for this and there was a consensus on stopping the community action, if running on forks

from hacktoberfest-practice.

Stale issue message

from hacktoberfest-practice.