Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heroku fail to deploy #835

Closed
doublep21 opened this issue May 8, 2022 · 4 comments
Closed

Heroku fail to deploy #835

doublep21 opened this issue May 8, 2022 · 4 comments
Labels
type: bug Seems like this is a bug

Comments

@doublep21
Copy link

Item could not be created:
We couldn't deploy your app because the source code violates the Salesforce Acceptable Use and External-Facing Services Policy.

@doublep21 doublep21 added the type: bug Seems like this is a bug label May 8, 2022
@brianferri
Copy link
Contributor

brianferri commented May 8, 2022

Please use the correct template to report a bug and fill everything you can out with the most detail possible:

Please describe the problem you are having in as much detail as possible:

Include a reproducible code sample here, if possible:

// Place your code here

Further details:

  • discord.js version:
  • Node.js version:
  • Operating system:
  • Priority this issue should have – please be realistic and elaborate if possible:

Relevant client options:

  • partials: none
  • gateway intents: none
  • other: none

@doublep21
Copy link
Author

Please use the correct template to report a bug and fill everything you can out with the most detail possible:

Please describe the problem you are having in as much detail as possible:

Include a reproducible code sample here, if possible:

// Place your code here

Further details:

  • discord.js version:
  • Node.js version:
  • Operating system:
  • Priority this issue should have – please be realistic and elaborate if possible:

Relevant client options:

  • partials: none
  • gateway intents: none
  • other: none

i didn't use it because i just used the link for heroku

@brianferri
Copy link
Contributor

i didn't use it because i just used the link for heroku

While I still think you should fill it out, The problem seems to be that someone has reported the repo on heroku and is being prevented from being forked.
The fix for this would be to (probably) rename the repo
at least according to this similar issue here

@DarrenOfficial
Copy link
Collaborator

Solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Seems like this is a bug
Projects
None yet
Development

No branches or pull requests

3 participants