Files
@ bce8e20057e1
Branch filter:
Location: kallithea/docs/contributing.rst - annotation
bce8e20057e1
1.9 KiB
text/prs.fallenstein.rst
repository summary: avoid table bleed on long commit messages
For commit messages with the first line being very long, the 'latest
changes' table on the repository overview page can 'bleed', so that the
commit number overlaps with the commit status.
Commit 15cb8156b10d732cf39b37a88c656894621c0f54 changed the initial truncate
on 50 characters to a chop at the first newline characters, causing this
issue to pop up more frequently.
Instead of using floating divs for the commit status and number of comments,
use dedicated table columns, as compact as possible.
Additionally, move these new columns to the very left of the table, instead
of cramming them in between the revision and commit message.
The comments-container class gets a new attribute 'white-space: nowrap' to
avoid the comment icon to wrap from the number of comments, when the table
does wrap on a small screen.
Note that the icon currently does not display as it should be renamed from
icon-comment-alt/colored to icon-comment. This will be fixed by Sean Farley.
For commit messages with the first line being very long, the 'latest
changes' table on the repository overview page can 'bleed', so that the
commit number overlaps with the commit status.
Commit 15cb8156b10d732cf39b37a88c656894621c0f54 changed the initial truncate
on 50 characters to a chop at the first newline characters, causing this
issue to pop up more frequently.
Instead of using floating divs for the commit status and number of comments,
use dedicated table columns, as compact as possible.
Additionally, move these new columns to the very left of the table, instead
of cramming them in between the revision and commit message.
The comments-container class gets a new attribute 'white-space: nowrap' to
avoid the comment icon to wrap from the number of comments, when the table
does wrap on a small screen.
Note that the icon currently does not display as it should be renamed from
icon-comment-alt/colored to icon-comment. This will be fixed by Sean Farley.
bb35ad076e2f bb35ad076e2f 17c9393e9645 e73a69cb98dc bb35ad076e2f bb35ad076e2f e73a69cb98dc 8af52e1224ff bb35ad076e2f 8af52e1224ff e73a69cb98dc 010e9532801a b53cef6faf22 b53cef6faf22 b53cef6faf22 e73a69cb98dc 053983a464e4 e73a69cb98dc e73a69cb98dc b53cef6faf22 010e9532801a 053983a464e4 e73a69cb98dc 950110f3f99f 950110f3f99f 950110f3f99f 8b8edfc25856 6fdc3b25bc7c 950110f3f99f b53cef6faf22 b53cef6faf22 b53cef6faf22 950110f3f99f 6fdc3b25bc7c 1b9d6b0a92b3 a9a1560dad79 b53cef6faf22 b53cef6faf22 b53cef6faf22 b53cef6faf22 b53cef6faf22 b53cef6faf22 b53cef6faf22 703d3208424c b53cef6faf22 b53cef6faf22 950110f3f99f 8af52e1224ff 9472a0150bf0 9472a0150bf0 9472a0150bf0 | .. _contributing:
=========================
Contributing to Kallithea
=========================
If you would like to contribute to Kallithea, please contact us, any help is
greatly appreciated!
Could I request that you make your source contributions by first forking the
Kallithea repository on bitbucket_
https://bitbucket.org/conservancy/kallithea and then make your changes to
your forked repository. Please post all fixes into **dev** bookmark since your
change might be already fixed there and i try to merge all fixes from dev into
stable, and not the other way. Finally, when you are finished with your changes,
please send us a pull request.
To run Kallithea in a development version you always need to install the latest
required libs. Simply clone Kallithea and switch to beta branch::
hg clone https://kallithea-scm.org/repos/kallithea
after downloading/pulling Kallithea make sure you run::
python setup.py develop
command to install/verify all required packages, and prepare development
enviroment.
There are two files in the directory production.ini and developement.ini copy
the `development.ini` file as rc.ini (which is excluded from version controll)
and put all your changes like db connection or server port in there.
After finishing your changes make sure all tests passes ok. You can run
the testsuite running ``nosetest`` from the project root, or if you use tox
run tox for python2.6-2.7 with multiple database test. When using `nosetests`
test.ini file is used and by default it uses sqlite for tests, edit this file
to change your testing enviroment.
There's a special set of tests for push/pull operations, you can runn them using::
paster serve test.ini --pid-file=test.pid --daemon
KALLITHEA_WHOOSH_TEST_DISABLE=1 KALLITHEA_NO_TMP_PATH=1 nosetests -x kallithea/tests/other/test_vcs_operations.py
kill -9 $(cat test.pid)
| Thank you for any contributions!
.. _bitbucket: http://bitbucket.org/
|