gitea/blog
46
20
Fork 32
Code Issues 10 Pull Requests Actions Activity

fix base64 csp error #279

Closed
HesterG wants to merge 2 commits from HesterG:fix-base64-csp into main
pull from: HesterG:fix-base64-csp
merge into: gitea:main
Conversation 4 Commits 2 Files Changed 5 +11 -11
5 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/post/creating-go-actions.md
View File

@ -74,7 +74,7 @@ jobs:
Since the action is written in Go and the `runs-on` environment may not have Go installed, you'll need to set up a Go runtime before using the action. The `setup-go` action works well in this case, but we'll discuss cases where it doesn't later. After pushing the workflow file, you can see the result in the Actions tab.
![use-go-action-main](/demos/creating-go-actions/use-go-action-main.png)
<img src='/demos/creating-go-actions/use-go-action-main.png' alt='use-go-action-main' />
## Inputs and Outputs
@ -168,7 +168,7 @@ jobs:
After pushing the updated workflow file, you will see the result:
![use-go-action-input-and-output](/demos/creating-go-actions/use-go-action-input-and-output.png)
<img src='/demos/creating-go-actions/use-go-action-input-and-output.png' alt='use-go-action-input-and-output' />
Good! You have successfully used `inputs` and `outputs` in your action.
You may find that the code for reading `inputs` and writing `outputs` looks complicated.
@ -288,11 +288,11 @@ jobs:
Then the workflow will work. You'll see the output of the `pre` in `Set up job`:
![go-action-pre](/demos/creating-go-actions/go-action-pre.png)
<img src='/demos/creating-go-actions/go-action-pre.png' alt='go-action-pre' />
and the output of the `post` in `Complete job`:
![go-action-post](/demos/creating-go-actions/go-action-post.png)
<img src='/demos/creating-go-actions/go-action-post.png' alt='go-action-post' />
---

2
content/post/release-of-1.11.0.md
View File

@ -65,7 +65,7 @@ _Thanks to [**@blueworrybear**](https://github.com/blueworrybear)_
## Issues can be closed/re-opened from pull requests ([#8866](https://github.com/go-gitea/gitea/pull/8866))
![reopen issue](/demos/8866/1.png)
<img src='/demos/8866/1.png' alt='reopen issue' />
_Thanks to [**@guillep2k**](https://github.com/guillep2k)_

4
content/post/release-of-1.20.0.md
View File

@ -340,13 +340,13 @@ If there are multiple files with the same name, the old UUID-based URLs will be
Previously each rendered timestamp would be static, now we show the real time since an event happend. If a comment was added 2 minutes before the page rendered it would show as "2 minutes ago" on the initial render and if another 8 minutes have passed, without a page refresh you'd see "10 minutes ago".
![Auto-updating duration timestamp](/demos/23988/auto-updating-timestamp.gif)
<img src='/demos/23988/auto-updating-timestamp.gif' alt='Auto-updating duration timestamp' />
Previously all timestamps would render in English, we now render these according to the user's chosen locale.
![German](/demos/23988/german-timestamp.png)
![Spanish](/demos/23988/spanish-timestamp.png)
<img src='/demos/23988/spanish-timestamp.png' alt='Spanish' />
### :rocket: Wildcards for required status checks in branch protection ([#24633](https://github.com/go-gitea/gitea/pull/24633))

2
content/post/release-of-1.4.0.md
View File

@ -54,7 +54,7 @@ _Thanks to **[@harryxu](https://github.com/harryxu)**_
## Progress bar for issues with checkboxes ([#3171](https://github.com/go-gitea/gitea/pull/3171))
![Progress bar demo](/demos/3171/1.png)
<img src='/demos/3171/1.png' alt='Progress bar demo' />
Issue lists in Gitea 1.4.0 show progress bars for issues that include checkboxes. Add checkboxes to your issue by typing `- [ ]` (unchecked state) or `- [X]` (checked state). This way, you can easily keep track of the progress you've made towards closing the issue.

6
content/post/release-of-1.5.0.md
View File

@ -63,8 +63,8 @@ _Thanks to [**@JonasFranzDEV**](https://github.com/JonasFranzDEV)_
## Issue Due Date ([#3794](https://github.com/go-gitea/gitea/pull/3794))
![Screenshot of issue due dates in the issue listing](/demos/3794/1.png)
![Form to add a due date](/demos/3794/2.png)
![Added issue date](/demos/3794/3.png)
<img src='/demos/3794/2.png' alt='Form to add a due date' />
<img src='/demos/3794/3.png' alt='Added issue date' />
Deadlines: following them is both the Project Manager's dream and the
Developer's nightmare. But, time and again it has been proven that they are,
@ -75,7 +75,7 @@ _Thanks to [**@kolaente**](https://github.com/kolaente)_
## Multiple Assignees ([#3705](https://github.com/go-gitea/gitea/pull/3705))
![Screenshot of 2 people being assigned to an issue.](/demos/3705/1.png)
<img src='/demos/3705/1.png' alt='Screenshot of 2 people being assigned to an issue.' />
In Gitea 1.5.0, you'll be able to assign multiple people to a single issue.
For cases where you'll need more manpower in order to understand the cryptic