mirror of
https://gitea.com/gitea/blog.git
synced 2024-06-02 02:41:23 +05:30
some adjustments
This commit is contained in:
HesterG
parent
692c3f5dad
commit
8c9ab0bd18
|
|
@ -129,9 +129,7 @@ wolfogre:
|
|||
title: Gitea maintainer
|
||||
url: https://gitea.com/wolfogre
|
||||
xinyu:
|
||||
image_url: https://gitea.com/xinyu.png
|
||||
name: xinyu
|
||||
url: https://gitea.com/xinyu
|
||||
yardenshoham:
|
||||
image_url: https://gitea.com/yardenshoham.png
|
||||
name: yardenshoham
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ Gitea's CI system, Gitea Actions, was recently released in version 1.19.0. Gitea
|
|||
Go actions provide a way for gophers who are not familiar with JavaScript to create native actions.
|
||||
However, compared to JavaScript actions, Go actions may be slower because they need to be built as executables before running. But you don't need to put the generated javascript files into dist in a Go action.
|
||||
|
||||
In this guide, we'll show you how to create a Go action in Gitea. Before diving in, you should have a basic understanding of Gitea Actions. If you're not familiar with it, we recommend reading [Hacking on Gitea Actions](https://blog.gitea.io/2023/03/hacking-on-gitea-actions/).
|
||||
In this guide, we'll show you how to create a Go action in Gitea. Before diving in, you should have a basic understanding of Gitea Actions. If you're not familiar with it, we recommend reading [Hacking on Gitea Actions](https://blog.gitea.com/hacking-on-gitea-actions/).
|
||||
|
||||
## A Simple Go Action
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ It should be noted that the information presented pertains to the current situat
|
|||
|
||||
## Usage
|
||||
|
||||
In [Feature Preview: Gitea Actions](https://blog.gitea.io/2022/12/feature-preview-gitea-actions/), we discussed how to try it out.
|
||||
In [Feature Preview: Gitea Actions](https://blog.gitea.com/feature-preview-gitea-actions/), we discussed how to try it out.
|
||||
However, some things have changed since then, so let's go over it again.
|
||||
|
||||
### Set up Gitea
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Thanks to votesUP, which allows for election observers, we were able to have enh
|
|||
|
||||
## Election Results
|
||||
The results of the ownership election yielded the same ownership team of the past year, where [@techknowlogick](https://gitea.com/techknowlogick), [@lunny](https://gitea.com/lunny), and [@zeripath](https://gitea.com/zeripath) were elected.
|
||||
As a followup from a [previous post](https://blog.gitea.io/2022/10/a-message-from-lunny-on-gitea-ltd.-and-the-gitea-project/), the maintainership team of the Gitea project has been in discussion over the past couple of months around what the future governance of the project looks like. These discussions resulted in the proposal of a governance charter for the project which was also voted on, and was passed with overwhelming support.
|
||||
As a followup from a [previous post](https://blog.gitea.com/a-message-from-lunny-on-gitea-ltd.-and-the-gitea-project/), the maintainership team of the Gitea project has been in discussion over the past couple of months around what the future governance of the project looks like. These discussions resulted in the proposal of a governance charter for the project which was also voted on, and was passed with overwhelming support.
|
||||
We'd like to send a sincere thank you to everyone who reached out and provided assistance and their experience with this process.
|
||||
The governance charter proposed a technical oversight comittee (TOC) which expands the ownership team of the Gitea project from the current three elected positions to six positions, where three would be elected as it happened over past years, and the other three would consist of appointed members from the company.
|
||||
|
||||
|
|
@ -81,7 +81,7 @@ The TOC and other maintainers are currently discussing the roadmap, but here is
|
|||
* Implement a high-availability concept
|
||||
|
||||
#### CI/CD
|
||||
* Polish and introduce/promote [Actions](https://blog.gitea.io/2022/12/feature-preview-gitea-actions/) to help ease migrations to Gitea and provide a small (but powerful!) optional CI
|
||||
* Polish and introduce/promote [Actions](https://blog.gitea.com/feature-preview-gitea-actions/) to help ease migrations to Gitea and provide a small (but powerful!) optional CI
|
||||
* Work on a better UX for third-party CI to be able to upload and view build logs in a unified interface
|
||||
|
||||
## TOC & Working groups
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ draft: false
|
|||
|
||||
We are proud to present the release of Gitea version 1.13.0.
|
||||
|
||||
As we approach Gitea's [4th birthday](https://blog.gitea.io/2016/12/release-of-1.0.0/), I just want to give a special thanks to everyone who has been a part of the project, whether it's the implementation of a feature, or just enjoying the software.
|
||||
As we approach Gitea's [4th birthday](https://blog.gitea.com/release-of-1.0.0/), I just want to give a special thanks to everyone who has been a part of the project, whether it's the implementation of a feature, or just enjoying the software.
|
||||
Thank you all!
|
||||
|
||||
We have merged an incredible [649](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+milestone%3A1.13.0+is%3Amerged) pull requests to release this version.
|
||||
|
|
|
|||
|
|
@ -133,7 +133,7 @@ jobs:
|
|||
|
||||
Huge thanks to the authors of actions ([@wolfogre](https://gitea.com/wolfogre), [@lunny](https://gitea.com/lunny), [@appleboy](https://gitea.com/appleboy) and [@fuxiaohei](https://gitea.com/fuxiaohei)), of [@nektos](https://github.com/nektos), [all contributors of act](https://github.com/nektos/act) for [act_runner](https://gitea.com/gitea/act_runner), and [@delvh](https://gitea.com/delvh) for significant effort spent reviewing the PRs.
|
||||
|
||||
More information can be found [in the issue to implement actions](https://github.com/go-gitea/gitea/issues/13539), and you can find a small tutorial [in our blog](https://blog.gitea.io/2022/12/feature-preview-gitea-actions/).
|
||||
More information can be found [in the issue to implement actions](https://github.com/go-gitea/gitea/issues/13539), and you can find a small tutorial [in our blog](https://blog.gitea.com/feature-preview-gitea-actions/).
|
||||
|
||||
### :rocket: Asciicast support ([#22448](https://github.com/go-gitea/gitea/issues/22448))
|
||||
It is now possible to view uploaded Asciicast (`.cast`) files.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ const darkCodeTheme = require('prism-react-renderer/themes/dracula');
|
|||
const config = {
|
||||
title: 'Gitea Blogs',
|
||||
tagline: 'Git with a cup of tea',
|
||||
favicon: 'img/favicon.png',
|
||||
favicon: 'img/favicon.svg',
|
||||
url: 'https://blog.gitea.com',
|
||||
baseUrl: '/',
|
||||
onBrokenLinks: 'warn',
|
||||
|
|
@ -25,9 +25,7 @@ const config = {
|
|||
showReadingTime: true,
|
||||
routeBasePath: '/',
|
||||
editUrl: 'https://gitea.com/gitea/blog/src/branch/main/',
|
||||
blogSidebarTitle: 'All posts',
|
||||
blogSidebarCount: 'ALL',
|
||||
postsPerPage: 10,
|
||||
postsPerPage: 12,
|
||||
path: 'content/post',
|
||||
blogTagsPostsComponent: require.resolve(
|
||||
"./src/theme/BlogListPage/index.js",
|
||||
|
|
@ -164,11 +162,7 @@ const config = {
|
|||
prism: {
|
||||
theme: lightCodeTheme,
|
||||
darkTheme: darkCodeTheme,
|
||||
},
|
||||
tableOfContents: {
|
||||
minHeadingLevel: 2,
|
||||
maxHeadingLevel: 2,
|
||||
},
|
||||
}
|
||||
}),
|
||||
};
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ import { Chip } from '../Chip';
|
|||
import styles from './styles.module.css';
|
||||
import { ensureTrailingSlash } from '@site/src/utils/ensureTrailingSlash.js';
|
||||
|
||||
export const Chips = ({ items, activeChip }) => (
|
||||
export const Chips = ({ items, activeChipLabel }) => (
|
||||
<div className={styles.root}>
|
||||
{items.map(({ label, permalink }) => (
|
||||
<Chip
|
||||
|
|
@ -11,7 +11,7 @@ export const Chips = ({ items, activeChip }) => (
|
|||
className={styles.chip}
|
||||
label={label}
|
||||
permalink={ensureTrailingSlash(permalink)}
|
||||
active={activeChip === permalink}
|
||||
active={activeChipLabel === label}
|
||||
/>
|
||||
))}
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ function BlogListPageContent(props) {
|
|||
<h2 className={styles.title}>Filter by Tag</h2>
|
||||
<div className={styles.categories}>
|
||||
<Chips
|
||||
activeChip={metadata.permalink}
|
||||
activeChipLabel={isTagsPage? props.tag.label: null}
|
||||
items={tags}
|
||||
/>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -11,6 +11,9 @@ import BlogPostPageMetadata from '@theme/BlogPostPage/Metadata';
|
|||
import TOC from '@theme/TOC';
|
||||
import styles from './styles.module.css';
|
||||
|
||||
// customized:
|
||||
// Hide toc
|
||||
// Added Cover Image to the post
|
||||
function BlogPostPageContent({sidebar, children}) {
|
||||
const {metadata, toc} = useBlogPost();
|
||||
const {nextItem, prevItem, frontMatter, title} = metadata;
|
||||
|
|
@ -21,15 +24,8 @@ function BlogPostPageContent({sidebar, children}) {
|
|||
} = frontMatter;
|
||||
return (
|
||||
<BlogLayout
|
||||
toc={
|
||||
!hideTableOfContents && toc.length > 0 ? (
|
||||
<TOC
|
||||
toc={toc}
|
||||
minHeadingLevel={tocMinHeadingLevel}
|
||||
maxHeadingLevel={tocMaxHeadingLevel}
|
||||
/>
|
||||
) : undefined
|
||||
}>
|
||||
sidebar={sidebar}
|
||||
>
|
||||
<BlogPostItem>
|
||||
{frontMatter.coverImage && <figure>
|
||||
<img
|
||||
|
|
|
|||
Binary file not shown.
|
Before Width: | Height: | Size: 4.2 KiB |
1
static/img/favicon.svg
Normal file
1
static/img/favicon.svg
Normal file
|
|
@ -0,0 +1 @@
|
|||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 640" style="enable-background:new 0 0 640 640" xml:space="preserve" width="32" height="32"><path style="fill:#fff" d="m395.9 484.2-126.9-61c-12.5-6-17.9-21.2-11.8-33.8l61-126.9c6-12.5 21.2-17.9 33.8-11.8 17.2 8.3 27.1 13 27.1 13l-.1-109.2 16.7-.1.1 117.1s57.4 24.2 83.1 40.1c3.7 2.3 10.2 6.8 12.9 14.4 2.1 6.1 2 13.1-1 19.3l-61 126.9c-6.2 12.7-21.4 18.1-33.9 12z"/><path style="fill:#609926" d="M622.7 149.8c-4.1-4.1-9.6-4-9.6-4s-117.2 6.6-177.9 8c-13.3.3-26.5.6-39.6.7v117.2c-5.5-2.6-11.1-5.3-16.6-7.9 0-36.4-.1-109.2-.1-109.2-29 .4-89.2-2.2-89.2-2.2s-141.4-7.1-156.8-8.5c-9.8-.6-22.5-2.1-39 1.5-8.7 1.8-33.5 7.4-53.8 26.9C-4.9 212.4 6.6 276.2 8 285.8c1.7 11.7 6.9 44.2 31.7 72.5 45.8 56.1 144.4 54.8 144.4 54.8s12.1 28.9 30.6 55.5c25 33.1 50.7 58.9 75.7 62 63 0 188.9-.1 188.9-.1s12 .1 28.3-10.3c14-8.5 26.5-23.4 26.5-23.4S547 483 565 451.5c5.5-9.7 10.1-19.1 14.1-28 0 0 55.2-117.1 55.2-231.1-1.1-34.5-9.6-40.6-11.6-42.6zM125.6 353.9c-25.9-8.5-36.9-18.7-36.9-18.7S69.6 321.8 60 295.4c-16.5-44.2-1.4-71.2-1.4-71.2s8.4-22.5 38.5-30c13.8-3.7 31-3.1 31-3.1s7.1 59.4 15.7 94.2c7.2 29.2 24.8 77.7 24.8 77.7s-26.1-3.1-43-9.1zm300.3 107.6s-6.1 14.5-19.6 15.4c-5.8.4-10.3-1.2-10.3-1.2s-.3-.1-5.3-2.1l-112.9-55s-10.9-5.7-12.8-15.6c-2.2-8.1 2.7-18.1 2.7-18.1L322 273s4.8-9.7 12.2-13c.6-.3 2.3-1 4.5-1.5 8.1-2.1 18 2.8 18 2.8L467.4 315s12.6 5.7 15.3 16.2c1.9 7.4-.5 14-1.8 17.2-6.3 15.4-55 113.1-55 113.1z"/><path style="fill:#609926" d="M326.8 380.1c-8.2.1-15.4 5.8-17.3 13.8-1.9 8 2 16.3 9.1 20 7.7 4 17.5 1.8 22.7-5.4 5.1-7.1 4.3-16.9-1.8-23.1l24-49.1c1.5.1 3.7.2 6.2-.5 4.1-.9 7.1-3.6 7.1-3.6 4.2 1.8 8.6 3.8 13.2 6.1 4.8 2.4 9.3 4.9 13.4 7.3.9.5 1.8 1.1 2.8 1.9 1.6 1.3 3.4 3.1 4.7 5.5 1.9 5.5-1.9 14.9-1.9 14.9-2.3 7.6-18.4 40.6-18.4 40.6-8.1-.2-15.3 5-17.7 12.5-2.6 8.1 1.1 17.3 8.9 21.3 7.8 4 17.4 1.7 22.5-5.3 5-6.8 4.6-16.3-1.1-22.6 1.9-3.7 3.7-7.4 5.6-11.3 5-10.4 13.5-30.4 13.5-30.4.9-1.7 5.7-10.3 2.7-21.3-2.5-11.4-12.6-16.7-12.6-16.7-12.2-7.9-29.2-15.2-29.2-15.2s0-4.1-1.1-7.1c-1.1-3.1-2.8-5.1-3.9-6.3 4.7-9.7 9.4-19.3 14.1-29-4.1-2-8.1-4-12.2-6.1-4.8 9.8-9.7 19.7-14.5 29.5-6.7-.1-12.9 3.5-16.1 9.4-3.4 6.3-2.7 14.1 1.9 19.8l-24.6 50.4z"/></svg>
|
||||
|
After Width: | Height: | Size: 2.2 KiB |
Loading…
Reference in a new issue