• Joined on 2023年11月23日
VewDev commented on issue forgejo/forgejo#6781 2025年12月04日 13:04:22 +01:00
feat: Filter to hide closed issues in project kanban board

This could also be extended to allow more complex filters. (Milestone, tags...)

VewDev commented on issue forgejo/discussions#131 2025年10月25日 09:51:43 +02:00
From Forking to Forging: Designing a modern contribution workflow for the future

I just came across this thread, and wanted to add my two cents on this.

VewDev commented on issue forgejo/forgejo#2177 2025年10月24日 10:17:13 +02:00
[FEAT] threaded replies on issue comments

As a side note, I believe comment threads should be allowed both in issue and PR comments, so it may make sense to merge code comment threads on PRs with this behavior.

VewDev commented on issue forgejo/forgejo#2177 2025年10月24日 10:04:14 +02:00
[FEAT] threaded replies on issue comments

It is unclear which comments you are referring to (are we talking about comments on tickets, on proposed changes or what?), but first, I wonder why you are talking about starting a new thread....

VewDev commented on issue forgejo/forgejo#9593 2025年10月18日 11:25:28 +02:00
bug: Directories in repo browser are only sort of lexicographically sorted

I agree on the multiple sorting UI options approach, even though this would require opening a feature request from this issue.

VewDev commented on issue forgejo/forgejo#7653 2025年10月16日 18:13:10 +02:00
Accessibility: Lots of pages lack headings

It would be great if you could provide a list of the pages you've found that are missing the HTML headers. I will take a look at the pages you've mentioned, as well as checking some other pages to...

VewDev commented on pull request forgejo/forgejo#8244 2025年10月16日 18:10:01 +02:00
fix: add dynamic aria-label to monospace button in markdown editor

@johnnyjayjay I could continue work on this PR if you wanted to.

VewDev commented on issue forgejo/forgejo#7671 2025年10月16日 18:02:35 +02:00
feat: Show the name from the user's profile for their commits instead of the name that's in git

Should this be worked on? I agree we should make it have the same behavior on all pages.

I agree that this should be implemented - but there's a obstacle that needs to be solved: there are...

VewDev pushed to forgejo at VewDev/forgejo 2025年10月16日 17:47:42 +02:00
5b13c6e024 fix: release email links (#9690)
fe4a2ae7c1 fix: empty DBs create tables in an ungoverned order resulting in future foreign key errors (#9709)
affadc359e fix: integration tests & empty DB creation will fail as soon as forgejo_migrations accesses an existing table (#9708)
8ed95dc4c6 fix: use scrollHeight for rendered iframe if offsetHeight is unavailable (#9508)
e56fdf1ec5 chore(release-notes): Forgejo v13.0.0 (#9442)
Compare 8 commits »
VewDev commented on issue forgejo/discussions#403 2025年10月16日 17:16:19 +02:00
Add new issue severity labels

Keep in mind that while the "priority" approach could also be applied to feature requests, there is already a 'gain\gain` structure that shows how important a feature request is.

VewDev opened issue forgejo/discussions#403 2025年10月16日 17:14:21 +02:00
Add new issue severity labels
VewDev commented on issue forgejo/forgejo#9593 2025年10月16日 12:50:46 +02:00
bug: Directories in repo browser are only sort of lexicographically sorted

There's also a chance someone tried to "01" < "0@", or any other allowed character.

I believe the comparison for the repo list tree should always order everything as a string, sorting in...

VewDev commented on issue forgejo/forgejo#9593 2025年10月16日 12:43:52 +02:00
bug: Directories in repo browser are only sort of lexicographically sorted

Wouldnt "01" < "0z" be false then?

Since "0z" couldnt be interpreted as hexadecimal, it would interpret them as decimals, and check if "01" < "0", returning false.

I might be wrong...

VewDev commented on issue forgejo/forgejo#9661 2025年10月16日 11:05:23 +02:00
bug: DEFAULT_EMAIL_NOTIFICATIONS defaults to enabled regardless of if email is set up

Another thought I had was to add an API endpoint that allows admins to manage the email_notifications_preference setting for users, rather than having to modify the database directly.

I don't...

VewDev commented on pull request forgejo/forgejo#9690 2025年10月16日 08:29:17 +02:00
fix: release email links

@mfenniak I have added a new commit fixing the formatting issue and all checks are apparently passing now

VewDev pushed to fix-release-email-link at VewDev/forgejo 2025年10月16日 08:21:13 +02:00
9489634c1c style: fix formatting consistency issues
VewDev commented on pull request forgejo/forgejo#9690 2025年10月15日 23:35:56 +02:00
fix: release email links

Okay so the Release object already had TarURL and ZipURL properties, and building a hyperlink in the template was not needed at all.

I have changed my commit to use those properties, and now...

VewDev pushed to fix-release-email-link at VewDev/forgejo 2025年10月15日 23:35:11 +02:00
63c2ce3de1 fix: release email links
VewDev commented on pull request forgejo/forgejo#9690 2025年10月15日 22:46:41 +02:00
fix: release email links

I have manually confirmed this

	<p>
		---
		<br>
		Downloads:
		<ul>
		=09
			<li>
				<a href=3D"http://localhost:3000/test/test/releases/tag/asd/archive/asd=
.zip" rel=3D"nofo...
VewDev pushed to forgejo at VewDev/forgejo 2025年10月15日 21:22:26 +02:00
6db2e23078 test: introduce TruncateBeansCascade test helper to support data cleanup of foreign-key referenced tables (#9684)
46e491f05e Update go-openapi packages (forgejo) (#9701)
ad70b09eea Update dependency happy-dom to v20 (forgejo) (#9703)
c5b292b635 Update module github.com/editorconfig-checker/editorconfig-checker/v3/cmd/editorconfig-checker to v3.4.1 (forgejo) (#9700)
Compare 18 commits »