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

iterative commit message instead of "Floccus bookmark update" #1757

Open
elvisisvan opened this issue Nov 2, 2024 · 2 comments
Open

iterative commit message instead of "Floccus bookmark update" #1757

elvisisvan opened this issue Nov 2, 2024 · 2 comments

Comments

@elvisisvan
Copy link

elvisisvan commented Nov 2, 2024

Describe the feature you'd like to request

this is an idea pitch for better assistance in version control management: interative/customized commit messages

Describe the solution you'd like

simple

instead of the same commit message "Floccus bookmark update" we can have iterations like 1, 2, 3, etc.
e.g. starting with "Floccus bookmark update 1" and as number of commits add up we'll have something like "Floccus bookmark update 234"

Describe alternatives you've considered

extensive

currently every commit by floccus has the same commit message, it's inconvenient to track changes by only commit name

floccus-commit-message

obsidian-git has a thing called placeholder so i can input custom properties like {{date}} for precise commit time and {{hostname}} for device name, i use "DESKTOP-1R97KDN" so i have this:

obsidian-commit-message

(you can see the full commit message in the 1st image above)

my suggestion is that we add placeholders for users to add custom values to a profile by themselves, that way can avoid possible failure and reduce complexity of querying browser-specific properties

Copy link

github-actions bot commented Nov 2, 2024

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved.
I'm Marcel and I created floccus a few years ago, maintaining it ever since. I currently work for Nextcloud
which leaves me with less time for side projects like this one than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient.
Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
To continue the development and maintenance of this project in a sustainable way it is expected that you donate to the project when opening a ticket,
if you're not a donor already. You can find donation options at https://floccus.org/donate/. Thank you!

One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

I look forward to working with you on this issue
Cheers 💙

@elvisisvan
Copy link
Author

reference issue: #1739
@metal450

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

No branches or pull requests

1 participant