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
Challenge:
----------
Libzypp supports parallel download and install. Yast installation progress does
not fit it at all [1]. Issues are secondary progress bar that does not work
with parallel installation. Also there are overwhelming amount of
information on screen that is quite distracting. That information is often
wrong like time estimation. And also table for media is a bit useless nowadays
as everything is on one iso/medium, so there is no need to see when cd switch
will be needed. The details tab are the most visible as it is default one.
Proposal:
---------
Remove completely that details tab and keep just release notes one[2]. It
contains release notes that contain useful information and also has just one
progress bar. For that bar remove keep always just remaining size and count of packages,
so user has idea how it does, but do not print what exactly is installing
or any time estimation. If there are more release notes allow to switch between them.
Also keep possibility to have slide show which we had in past for installation
if someone create some ( when checked other OSes, the Ubuntu slide show during
installation looks probably the best from user POV ).
The same changes will apply to ncurses front end[3], we just need to check why formatting
of release notes are so badly formatted.
And same for opensuse[4] of course.
Josef
[1] https://pasteboard.co/cNBjER6SnLLT.png
[2] https://pasteboard.co/WnI7wS7VVVqq.png
[3] https://pasteboard.co/vzQvY1PaVDaD.png
[4] https://pasteboard.co/FzEqcIN7Xnas.png
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
> Marc Chamberlin composed on 2021-12-30 16:08 (UTC-0800):
>>> Optane
Original thread:
<https://lists.opensuse.org/archives/list/users@lists.opensuse.org/thread/D3…>
This problem is really one that belongs on the factory list, where some dev is apt
to notice; and in a bug report. An Optane SSD should not cause the partitioner to
hang. Optane is several years old, about 4 Intel CPU generations.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
Year 2021 comes to an end, but not before the YaST Team publishes
another development report covering areas as diverse as:
- Improvements in the installer self-update mechanism
- Better error reporting in storage analysis
- More consistent management of UEFI
- Better handling of the installer boot arguments
- More intuitive representation of thin logical volumes
Check the full post at:
https://yast.opensuse.org/blog/2021-12-20/sprint-137
Cheers
--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
Hi all,
Lately, we have been discussing what information YaST should display
while installing the system[1]. After considering everything and asking
for help from our UX experts, we have decided to start with a
minimalistic approach. The idea is to show only the progress bar (with
a description, of course, of the current step). So no slideshow, no
release notes, no tabs, etc.
Additionally, we are integrating the steps in the final screen into the
progress bar.
Once we have feedback from our users, we can think about extending the
solution to display additional info.
## Notes
However, we had a nice discussion before reaching that conclusion. So I
am sharing a few notes from the meeting.
* Release notes:
+ Do our users read the release notes during installation?
+ An add-on can have release notes, so YaST uses tabs to display all
the release notes (base product and add-ons).
+ Release notes are available at other points of the installation
through a button. So we do not need to show them while installing
packages.
* The slideshow:
+ We could get good quality content from
https://suse-projects.github.io/ to build a slideshow.
+ That content will be updated regularly by the marketing team.
+ Using the content during installation is not that straightforward.
For instance, in many environments, the system under installation
cannot access the Internet.
+ Additionally, we need to consider other stuff like screenshots,
translations, and so on.
* Tabs & buttons:
+ We use tabs to show the slideshow and the release notes. It feels
like mixing different stuff. What about using another mechanism to
display release notes?
+ Displaying the release notes in a pop-up window will not work
because the installer will not update the progress bar until the pop-up
is closed. It is a known limitation we need to deal with.
Regards,
Imo
[1]
https://lists.opensuse.org/archives/list/yast-devel@lists.opensuse.org/thre…
--
Imobach González Sosa
YaST Team at SUSE LLC
https://imobachgs.github.io/
This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet.
Pending requests in repository yast-country:
- WIP: First very rough table extension for new keymaps (17 days)
https://github.com/yast/yast-country/pull/288
Pending requests in repository yast-devtools:
- Set %yast_icondir to /usr/share/icons/hicolor (bsc#1186066) (130 days)
https://github.com/yast/yast-devtools/pull/161
Pending requests in repository yast-sound:
- Fix module filename matching (jsc#SLE-21256). (13 days)
https://github.com/yast/yast-sound/pull/53
Pending requests in repository yast-journal:
- Use Yast::Builtins.strftime in 'Change Filter' dialog (62 days)
https://github.com/yast/yast-journal/pull/45
Pending requests in repository skelcd-control-MicroOS:
- keylime: remove ALPHA tag (10 days)
https://github.com/yast/skelcd-control-MicroOS/pull/43
Pending requests in repository yast-sap-ha:
- SUSE SAP HA Yast wizard for HANA doesn´t configure the HANA hooks. (47 days)
https://github.com/yast/yast-sap-ha/pull/8
- SUSE SAP HA Yast wizard for HANA doesn´t configure the HANA hooks. (42 days)
https://github.com/yast/yast-sap-ha/pull/7