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

New Sheet - GhostBusterInternationalR20 #13540

Closed
wants to merge 33 commits into from
Closed

Conversation

Cacealeos
Copy link
Contributor

Submission Checklist

Required

  • [x ] The pull request title clearly contains the name of the sheet I am editing.
  • [ x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
  • [ x] The pull request makes changes to files in only one sub-folder.
  • [x ] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

  • The name of this game is: < GhostBusterInternationalR20 > (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

  • The publisher of this game is: < IDW > (i.e. Wizards of the Coast, Evil Hat)

  • The name of this game system/family is: < > (i.e. Dungeons & Dragons, FATE)

  • [ x] I have followed the Character Sheets Standards when building this sheet.

  • I have authorization from the game's publisher to make this an official sheet on Roll20 with their name attached.
  • This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: < >
  • This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Sheet request by another user

@Cacealeos
Copy link
Contributor Author

How can I remove the other commit from this branch? I can't seem to fork the repo twice

@NorWhal
Copy link
Contributor

NorWhal commented Nov 26, 2024

Hi @Cacealeos!

I'd start a new branch on your forked repo and cherry-pick your Ghostbuster International Edition commit from this branch. Once that's done, you can make a PR from that branch. You may need to take your other changes, move them to a different branch, and reset master to before you started work on Generation before you do this.

@NorWhal
Copy link
Contributor

NorWhal commented Nov 26, 2024

Given that this is going to necessitate a new PR, I will go ahead and close this one.

@NorWhal NorWhal closed this Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants