Contributing to Obsidian Portable
Thank you for your interest in contributing to Obsidian Portable! This project is maintained by @Papela and the community.Ways to Contribute
There are several ways you can help improve Obsidian Portable:Report Issues
Found a bug? Let us know by opening an issue on GitHub
Submit Code
Contribute code improvements via pull requests
Improve Docs
Help improve documentation and help files
Support Development
Support the project financially through Ko-fi
Code Contributions
If you want to contribute code to this project, follow these steps:Fork the Repository
Fork the Obsidian Portable repository to your GitHub account
Create a Feature Branch
Create a branch for your new feature or bug fixUse a descriptive branch name that explains what you’re working on, such as:
fix-launcher-crashadd-auto-updateimprove-settings-dialog
Make Your Changes
Make your changes and commit them with clear, descriptive commit messages
Write clear commit messages that explain why the change was made, not just what was changed.
Open a Pull Request
Go to the original repository on GitHub and open a pull requestIn your pull request:
- Clearly describe what your changes do
- Reference any related issues
- Explain why the changes are needed
- Include screenshots if relevant
Reporting Issues
When reporting issues, please provide:- Clear Description: Explain what’s wrong and what you expected to happen
- Steps to Reproduce: List the exact steps to reproduce the issue
- Environment Details:
- Windows version
- Obsidian Portable version
- Location (USB drive, cloud folder, local drive)
- Error Messages: Include any error messages or logs
- Screenshots: If applicable, add screenshots to help explain the problem
Good Issue Example
Documentation Contributions
Help improve the documentation by:- Fixing typos or unclear explanations
- Adding missing information
- Creating tutorials or guides
- Improving help.html content
- Translating documentation
Code Guidelines
When contributing code, please follow these guidelines:Code Style
Code Style
- Follow the existing code style in the project
- Use consistent indentation (spaces or tabs as per existing files)
- Comment complex logic
- Keep functions focused and modular
Testing
Testing
- Test your changes thoroughly before submitting
- Test on different Windows versions if possible
- Test from different locations (USB, local, network)
- Verify upgrade scenarios work correctly
Compatibility
Compatibility
- Ensure changes work with PortableApps.com launcher
- Maintain compatibility with existing installations
- Don’t break existing user data or settings
- Consider backward compatibility
Documentation
Documentation
- Update help.html if user-facing features change
- Update README.md if necessary
- Add comments explaining why code works a certain way
- Document any new configuration options
Financial Support
If you’d like to support the project financially:Support Papela
Support the portable packaging maintainer
Support Obsidian
Support Obsidian development
Support PortableApps
Support PortableApps.com hosting
Community Guidelines
When participating in the Obsidian Portable community:- Be Respectful: Treat everyone with respect and professionalism
- Be Constructive: Provide constructive feedback and suggestions
- Be Patient: Maintainers are often volunteers with limited time
- Be Helpful: Help other users when you can
- Follow Guidelines: Follow GitHub’s community guidelines and code of conduct
License
By contributing to Obsidian Portable, you agree that your contributions will be licensed under the GPL-3.0 License.All contributions are subject to review and may be modified or rejected at the maintainer’s discretion.
Questions?
If you have questions about contributing:- Check the FAQ for common questions
- Open a discussion on GitHub
- Review existing pull requests for examples
