-
Notifications
You must be signed in to change notification settings - Fork 79
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
Support relative media paths #214
Comments
There is nothing stopping folks from putting subdirectories within the |
I understand that the media folder can also be nested, but why force users to keep media and tweets in separate places? Allowing associated files to exist next to each other in the same folder helps keep the directory structure DRY, organization is easier and less confusing for contributors, especially for larger projects.
Instead of
|
Ah yeah true, I could see it being a bit of a pain to have a dedicated media directory if someone were using this action in a repo that were doing things other than just tweets etc. I wonder if the best approach might be to accept a path as it is currently (e.g. |
What’s missing?
Currently media uploads need to be in a top level
media
directory.To giver users optionality in how they organize their projects, they should be able to specify a relative file path for media uploads, allowing media to be organized alongside their relevant
.tweet
files with thetweets
directory.Why?
For projects with many tweets, especially with nested directories, a separate top level
media
folder may become disorganized, and specifying unique names for each file may be confusing.The text was updated successfully, but these errors were encountered: