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

added movement-tracker #30

Merged
merged 2 commits into from
Sep 21, 2023
Merged

Conversation

ismager7878
Copy link
Contributor

@ismager7878 ismager7878 commented Aug 13, 2023

Make sure that your submission has the following:

  • A link to the raw github markdown file with a YAML front matter definition containing:
    • The title of your extension
    • A description of your extension
    • The author
    • A hero image
    • An icon
    • Tags (these will help with your extension's discoverability)
    • A link to your extensions manifest

Please, go through these steps before you submit a PR.

  • You have done your changes in a separate branch.

  • You have a descriptive commit message with a short title (first line).

  • You have only one commit (if not, squash them into one commit).

  • Your pull request MUST target the main branch on this repository.

  • Your pull request puts your extensions details as the last entry in the extensions.json file

@mitchemmc mitchemmc merged commit 42c5acf into owlbear-rodeo:main Sep 21, 2023
@ismager7878
Copy link
Contributor Author

Hi thanks for accepting my extension. I noticed that my assets in the referenced in markdown file wasn't showing on the extension page. I apparently by mistake used local paths as asset references in the file. This is fixed now, and the current public markdown is now using public links instead, if you at any point would like to update it:)

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