Hi,
I found a quite interesting tool called Overcommit [1].
It provides an easy way for setting up Git commit hooks and provides
some basic checking plugins.
The nice feature of the Git commit hooks is that you can run some checks
automatically and early in the development. For example with the commit hooks you can
run Rubocop check automatically whenever a commit is created. And if the check fails
the commit is not created.
I can see "make Rubocop happy" commits quite often (happens to me as well),
with Overcommit you can easily avoid that.
I have tried several Overcommit checks:
- Rubocop - runs Rubocop at "commit"
- Rspec - runs the tests before "push"
- Branch blacklist - can forbid direct commits to configured branches,
e.g. "master" (forces using pull requests, avoids commits to master my mistake)
- Commit message spellcheck - warns when there is a possible typo
Check my blog post [2] for the details, esp. watch the recorded screencast where
I wanted to show some mistakes which it can catch.
The tool looks promising, I'll try using it for some time. If you want to try it
as well check the blog post for the installation steps.
Enjoy!
[1] https://github.com/brigade/overcommit
[2] http://blog.ladslezak.cz/2016/06/06/overcommit/
--
Ladislav Slezák
Appliance department / YaST Developer
Lihovarská 1060/12
190 00 Prague 9 / Czech Republic
tel: +420 284 028 960
lslezak(a)suse.com
SUSE
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi all,
some time ago we discussed where and how we should share
"Tips&Tricks" for YaST users and developers.
IIRC there was no clear conclusion so I decided to start
a wiki [1] to collect all our tricks we know or use.
For now it's just a place for dumping your ideas, links, short
howtos, etc... When we collect enough data we can probably
split it to several categories or move it somewhere else.
We just need the data first.
I have added there some my tricks from my personal "knowledgebase"
file. If you have better tricks or find something wrong simply
change it, it's a wiki ;-)
Ladislav
[1] https://github.com/yast/yast.github.io/wiki/YaST-Tips-and-Tricks
--
Ladislav Slezák
YaST Developer
SUSE LINUX, s.r.o.
Corso IIa
Křižíkova 148/34
18600 Praha 8
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
please add the new YaST package yast2-usbauth from
https://github.com/kochstefan/yast-usbauth or
https://build.opensuse.org/package/show/home:kochstefan/yast2-usbauth to
openSUSE Tumbleweed.
This work was initially created for SUSE in 2015. Part of it was the USB
interface authorization for the Linux kernel. It's contained in Linux
since kernel version 4.4. The packages libusbauth-configparser, usbauth
and usbauth-notifier are already part of openSUSE Tumbleweed.
packages from the usbauth development:
- libusbauth-configparser is a library that is used to parse the usbauth
config file.
- usbauth is a firewall against BadUSB attacks. It allows/denies USB
interfaces using a config file. The needed USB interface authorization
is part of Linux 4.4 and newer.
- usbauth-notifier is a graphical notifier for user interaction to allow
or deny USB devices.
- yast2-usbauth: is a YaST module to edit the usbauth configuration file
Thank you.
Best regards
Stefan Koch
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi all,
I am Joaquín and I am working on a rewrite of YaST keyboard module, info
here [1]. In a nutshell, I am writing a keyboard module for YaST with
ruby using OOD, with an implementation for SystemD.
Right now i am looking to map the code of every keyboard layout (for
example: us, es, us-dvorak) with their human readable translation (
“English (US)”, “Spanish”,...), but i have some questions about it.
I have taken a look to the existing code to try to use the same
translations. And i found two files, “keyboard_raw_opensuse.ycp” and
“keyboard_raw.ycp”. Also i found the part of the code that is using one
of these two files [2]. The only difference between these files i see,
is that in some cases, for a language one file uses a .map.gz file and
the other use a different .map.gz, for example with “spanish-lat” see
[3] and [4].
I think that with only one map for each code is enough for an
implementation with SystemD but i am not sure, because I don’t
understand the reason of these differences in the current module. It
would be nice if some of you can explain to me so i can understand it,
and apply a good solution in the project.
Also in the case that is only needed one mapping, which of those files
should i take as reference?
Thank you all,
Joaquín
[1] https://github.com/openSUSE/mentoring/issues/79
[2]
https://github.com/yast/yast-country/blob/master/keyboard/src/modules/Keybo…
[3]https://github.com/yast/yast-country/blob/master/keyboard/src/data/keyboa…
[4]https://github.com/yast/yast-country/blob/master/keyboard/src/data/keyboa…
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Back from the openSUSE Conference preceded by a team workshop, the YaST
team strikes back with another report from the trenches. Check all the
last-minutes improvements for Leap 15.0 and SLE15.
https://lizards.opensuse.org/2018/05/31/yast-sprint-57/
Cheers.
--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org