Skip to content

Commit 48c9ece

Browse files
ivictborivictbor
committed
Deploy website - based on 7e6d6b80c1a3cfe37013f36b723b86abe2cb39e4
1 parent e60c542 commit 48c9ece

File tree

139 files changed

+218
-148
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

139 files changed

+218
-148
lines changed

‎404.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@
1616
<link rel="search" type="application/opensearchdescription+xml" title="Vue &amp; Node admin panel framework" href="/opensearch.xml">
1717

1818
<script src="/scripts/adminforth.js"></script><link rel="stylesheet" href="/assets/css/styles.ba19fe4b.css">
19-
<script src="/assets/js/runtime~main.876b76ad.js" defer="defer"></script>
19+
<script src="/assets/js/runtime~main.895f5587.js" defer="defer"></script>
2020
<script src="/assets/js/main.ceb76142.js" defer="defer"></script>
2121
</head>
2222
<body class="navigation-with-keyboard">

‎assets/js/05019ff2.7b1ad307.js renamed to ‎assets/js/05019ff2.75f8cb3f.js

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎assets/js/bfc602de.dd94d0f9.js renamed to ‎assets/js/bfc602de.0d588026.js

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎assets/js/dbfc4782.1a099e98.js

Lines changed: 1 addition & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎assets/js/dbfc4782.aa3e11f5.js

Lines changed: 0 additions & 1 deletion
This file was deleted.

‎assets/js/runtime~main.876b76ad.js renamed to ‎assets/js/runtime~main.895f5587.js

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎blog/ai-blog/index.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@
1616
<link rel="search" type="application/opensearchdescription+xml" title="Vue &amp; Node admin panel framework" href="/opensearch.xml">
1717

1818
<script src="/scripts/adminforth.js"></script><link rel="stylesheet" href="/assets/css/styles.ba19fe4b.css">
19-
<script src="/assets/js/runtime~main.876b76ad.js" defer="defer"></script>
19+
<script src="/assets/js/runtime~main.895f5587.js" defer="defer"></script>
2020
<script src="/assets/js/main.ceb76142.js" defer="defer"></script>
2121
</head>
2222
<body class="navigation-with-keyboard">

‎blog/archive/index.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@
1616
<link rel="search" type="application/opensearchdescription+xml" title="Vue &amp; Node admin panel framework" href="/opensearch.xml">
1717

1818
<script src="/scripts/adminforth.js"></script><link rel="stylesheet" href="/assets/css/styles.ba19fe4b.css">
19-
<script src="/assets/js/runtime~main.876b76ad.js" defer="defer"></script>
19+
<script src="/assets/js/runtime~main.895f5587.js" defer="defer"></script>
2020
<script src="/assets/js/main.ceb76142.js" defer="defer"></script>
2121
</head>
2222
<body class="navigation-with-keyboard">

‎blog/atom.xml

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -159,7 +159,17 @@ For our internal team we use Slack and we want to get notifications about releas
159159
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="should-i-maintain-changelogmd-anymore">Should I maintain CHANGELOG.md anymore?<a href="https://adminforth.dev/blog/why-manual-release-notes-and-versions-are-a-chaos-and-how-to-fix-it/#should-i-maintain-changelogmd-anymore" class="hash-link" aria-label="Direct link to Should I maintain CHANGELOG.md anymore?" title="Direct link to Should I maintain CHANGELOG.md anymore?">​</a></h2>
160160
<p><code>semantic-release</code> has a plugin for generating not only GitHub release notes, but also CHANGELOG.md.</p>
161161
<p>Since previusly we used CHANGELOG.md I thought it would be good to have it in project. But once I entered <a href="https://github.com/semantic-release/changelog" target="_blank" rel="noopener noreferrer">plugin page</a> I got a notice which <a href="https://semantic-release.gitbook.io/semantic-release/support/faq#should-release-notes-be-committed-to-a-changelog.md-in-my-repository-during-a-release" target="_blank" rel="noopener noreferrer">explained complexity</a> added for this approach.</p>
162-
<p>So we ended with a simple <a href="https://github.com/devforth/adminforth/blob/main/CHANGELOG.md" target="_blank" rel="noopener noreferrer">link to GitHub releases</a></p>]]></content>
162+
<p>So we ended with a simple <a href="https://github.com/devforth/adminforth/blob/main/CHANGELOG.md" target="_blank" rel="noopener noreferrer">link to GitHub releases</a></p>
163+
<h2 class="anchor anchorWithStickyNavbar_LWe7" id="is-it-all-that-good">Is it all that good?<a href="https://adminforth.dev/blog/why-manual-release-notes-and-versions-are-a-chaos-and-how-to-fix-it/#is-it-all-that-good" class="hash-link" aria-label="Direct link to Is it all that good?" title="Direct link to Is it all that good?">​</a></h2>
164+
<p>Well, there are no perfect approaches in the world.</p>
165+
<p>Of course <code>semantic-release</code> has some cons.</p>
166+
<p>First of all, while you can write a commit messages without any prefix and they will not be included in release, you still have to follow strict commit message format when you are releasing feature or fix. And you don't have to forget to use this format. Instead of making manual forming of release notes which is done by one person, now every developer in team has to follow the same format and has to write clear commit messages.</p>
167+
<p>And there are couple of bad things with last points:</p>
168+
<ul>
169+
<li>It is not so easy to modify commit message once it is pushed to GitHub, so commit writing becomes one of the most critical parts of development process where you have to be very careful.</li>
170+
<li>Commit message should be understood not only by developers of framework, but also by users of framework. And some developers might think that these are two absolutely different dementions of understanding: first one is for developers, second one is for users. But in fact, at AdminForth, we think that set of user-friendly commit messages is a very small subset of set of developer-friendly commit messages. So if you write user-friendly commit messages, there is no chance that developers will not understand them.</li>
171+
</ul>
172+
<p>You are still fine with merging incoming PRs and ignore their commit messages becuse GitHub allows to edit commit message before merging ( using <code>Squash and merge</code> option )</p>]]></content>
163173
<author>
164174
<name>Ivan Borshcho</name>
165175
<uri>https://github.com/ivictbor</uri>

‎blog/authors/index.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@
1616
<link rel="search" type="application/opensearchdescription+xml" title="Vue &amp; Node admin panel framework" href="/opensearch.xml">
1717

1818
<script src="/scripts/adminforth.js"></script><link rel="stylesheet" href="/assets/css/styles.ba19fe4b.css">
19-
<script src="/assets/js/runtime~main.876b76ad.js" defer="defer"></script>
19+
<script src="/assets/js/runtime~main.895f5587.js" defer="defer"></script>
2020
<script src="/assets/js/main.ceb76142.js" defer="defer"></script>
2121
</head>
2222
<body class="navigation-with-keyboard">

0 commit comments

Comments
 (0)