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

Fix problem with static paths #10874

Merged
merged 1 commit into from
Mar 29, 2022
Merged

Fix problem with static paths #10874

merged 1 commit into from
Mar 29, 2022

Conversation

QveenSi-zz
Copy link

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • [+] Bug fix (non-breaking change which fixes an issue)
  • [-] New feature (non-breaking change which adds functionality)
  • [-] Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • [-] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • [+] Test A
  • [+] Test B

Test Configuration:

  • PHP version: 7.4
  • MySQL version: 5.6
  • Webserver version: nginx/1.16.1
  • OS version: Ubuntu 20.04

Checklist:

  • [+] I have read the Contributing documentation available here: https://snipe-it.readme.io/docs/contributing-overview
  • [+] I have formatted this PR according to the project guidelines: https://snipe-it.readme.io/docs/contributing-overview#pull-request-guidelines
  • [+] My code follows the style guidelines of this project
  • [+] I have performed a self-review of my own code
  • [-] I have commented my code, particularly in hard-to-understand areas
  • [-] I have made corresponding changes to the documentation
  • [+] My changes generate no new warnings
  • [-] I have added tests that prove my fix is effective or that my feature works
  • [+] New and existing unit tests pass locally with my changes

@QveenSi-zz QveenSi-zz requested a review from snipe as a code owner March 27, 2022 20:18
@welcome
Copy link

welcome bot commented Mar 27, 2022

💖 Thanks for this pull request! 💖

We use semantic commit messages to streamline the release process and easily generate changelogs between versions. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix if it doesn't have one already.

Examples of commit messages with semantic prefixes:

  • Fixed #<issue number>: don't overwrite prevent_default if default wasn't prevented
  • Added #<issue number>: add checkout functionality to assets
  • Improved Asset Checkout: use new notification method for checkout

Things that will help get your PR across the finish line:

  • Document any user-facing changes you've made.
  • Include tests when adding/changing behavior.
  • Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

@snipe
Copy link
Owner

snipe commented Mar 29, 2022

Looks great, thanks! (Some paths had changed from the time that script was utilized and when S3 was kinda ready.)

@snipe snipe merged commit e046db6 into snipe:master Mar 29, 2022
@welcome
Copy link

welcome bot commented Mar 29, 2022

Congrats on merging your first pull request! 🎉🎉🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants