profile
viewpoint

kevva/download 982

Download and extract files

Mottie/GitHub-userscripts 732

Userscripts to add functionality to GitHub

mafintosh/dns-packet 103

An abstract-encoding compliant module for encoding / decoding DNS packets

mafintosh/dns-socket 84

Make custom low-level DNS requests from node with retry support.

silverwind/armhf-registry 7

Minimal Docker Registry image the ARM architecture

silverwind/as-networks 5

Get all CIDR networks contained in an autonomous system

silverwind/caa 4

rfc6844-conform CAA record lookup and validation

silverwind/cfdns 3

CLI to modify DNS records hosted on Cloudflare

6543-forks/gitea 0

Git with a cup of tea, painless self-hosted git service

mrsdizzie/gitea 0

Git with a cup of tea, painless self-hosted git service

push eventStylishThemes/GitHub-Dark

github-actions[bot]

commit sha a9180a31d2b069c6d0d62b1cacbb83e8efb4aac3

automated regeneration

view details

github-actions[bot]

commit sha 6d8ef5038a69d21012f564ab83363931331c0155

v2.0.96 * automated regeneration (github-actions[bot]) * Add node_modules dependencies to make targets (silverwind)

view details

push time in 5 hours

created tagStylishThemes/GitHub-Dark

tagv2.0.96

:octocat: Dark GitHub style

created time in 5 hours

issue openednippur72/ifdef-loader

Define environment variables by default

I think it'd make sense to define everything in process.env by default, so instead of

/// #if env == 'PRODUCTION'
/// #if PRODUCTION

one can do a more standard

/// #if NODE_ENV === 'production'
/// #if process.env.NODE_ENV === 'production'

Variables defined in options should overwrite bare variables like NODE_ENV but process.env should always reflect the actual environment.

I imagine this would allow to integrate the loader with default options in most cases.

created time in 8 hours

Pull request review commentgo-gitea/gitea

Show full GPG commit status on PR commit history

 					{{$class = (printf "%s%s" $class " isWarning")}} 				{{end}} 			{{end}}-			{{if $.Issue.PullRequest.BaseRepo.Name}}-				<a href="{{AppSubUrl}}/{{$.Issue.PullRequest.BaseRepo.OwnerName}}/{{$.Issue.PullRequest.BaseRepo.Name}}/commit/{{.ID}}" rel="nofollow" class="{{$class}}">+			{{if $.comment.Issue.PullRequest.BaseRepo.Name}}+				<a href="{{AppSubUrl}}/{{$.comment.Issue.PullRequest.BaseRepo.OwnerName}}/{{$.comment.Issue.PullRequest.BaseRepo.Name}}/commit/{{.ID}}" rel="nofollow" class="{{$class}}"> 			{{else}} 				<span class="{{$class}}"> 			{{end}}-					<span class="shortsha">{{ShortSha .ID.String}}</span>-			{{if $.Issue.PullRequest.BaseRepo.Name}}+			<span class="shortsha">{{ShortSha .ID.String}}</span>+			{{if .Signature}}+				<div class="ui detail icon button">+					{{if .Verification.Verified}}+						<div title="{{if eq .Verification.TrustStatus "trusted"}}{{else if eq .Verification.TrustStatus "untrusted"}}{{$.root.i18n.Tr "repo.commits.signed_by_untrusted_user"}}: {{else}}{{$.root.i18n.Tr "repo.commits.signed_by_untrusted_user_unmatched"}}: {{end}}{{.Verification.Reason}}">+						{{if ne .Verification.SigningUser.ID 0}}+							<i class="lock icon"></i>+							<img class="ui signature avatar image" src="{{.Verification.SigningUser.RelAvatarLink}}" />+						{{else}}+							<i title="{{.Verification.Reason}}" class="icons">+								<i class="lock icon"></i>+								<i class="tiny inverted cog icon centerlock"></i>+							</i>+							<img class="ui signature avatar image" src="{{AvatarLink .Verification.SigningEmail}}" />+						{{end}}+						</div>+					{{else}}+						<i title="{{$.root.i18n.Tr .Verification.Reason}}" class="unlock icon"></i>+					{{end}}+				</div>

Looking good at first glance. Will test later.

CirnoT

comment created time in 8 hours

delete branch silverwind/gitea

delete branch : edge-version

delete time in 9 hours

Pull request review commentgo-gitea/gitea

Show full GPG commit status on PR commit history

 					{{$class = (printf "%s%s" $class " isWarning")}} 				{{end}} 			{{end}}-			{{if $.Issue.PullRequest.BaseRepo.Name}}-				<a href="{{AppSubUrl}}/{{$.Issue.PullRequest.BaseRepo.OwnerName}}/{{$.Issue.PullRequest.BaseRepo.Name}}/commit/{{.ID}}" rel="nofollow" class="{{$class}}">+			{{if $.comment.Issue.PullRequest.BaseRepo.Name}}+				<a href="{{AppSubUrl}}/{{$.comment.Issue.PullRequest.BaseRepo.OwnerName}}/{{$.comment.Issue.PullRequest.BaseRepo.Name}}/commit/{{.ID}}" rel="nofollow" class="{{$class}}"> 			{{else}} 				<span class="{{$class}}"> 			{{end}}-					<span class="shortsha">{{ShortSha .ID.String}}</span>-			{{if $.Issue.PullRequest.BaseRepo.Name}}+			<span class="shortsha">{{ShortSha .ID.String}}</span>+			{{if .Signature}}+				<div class="ui detail icon button">+					{{if .Verification.Verified}}+						<div title="{{if eq .Verification.TrustStatus "trusted"}}{{else if eq .Verification.TrustStatus "untrusted"}}{{$.root.i18n.Tr "repo.commits.signed_by_untrusted_user"}}: {{else}}{{$.root.i18n.Tr "repo.commits.signed_by_untrusted_user_unmatched"}}: {{end}}{{.Verification.Reason}}">+						{{if ne .Verification.SigningUser.ID 0}}+							<i class="lock icon"></i>+							<img class="ui signature avatar image" src="{{.Verification.SigningUser.RelAvatarLink}}" />+						{{else}}+							<i title="{{.Verification.Reason}}" class="icons">+								<i class="lock icon"></i>+								<i class="tiny inverted cog icon centerlock"></i>+							</i>+							<img class="ui signature avatar image" src="{{AvatarLink .Verification.SigningEmail}}" />+						{{end}}+						</div>+					{{else}}+						<i title="{{$.root.i18n.Tr .Verification.Reason}}" class="unlock icon"></i>+					{{end}}+				</div>

Would it make sense to extract this badge to its own template file? This is the third occurence of it. DRY 😉

CirnoT

comment created time in 9 hours

pull request commentgo-gitea/gitea

Fix timezone on issue deadline

Can we keep the format change to YYYY-MM-DD? I don't like this inconsistency in the date formats.

// FormatDate formats a date in YYYY-MM-DD server time zone
func (ts TimeStamp) FormatDate() string {
  return time.Unix(int64(ts), 0).String()[:10]
}

And use that instead of formatShort in templates/repo/issue/view_content/sidebar.tmpl.

CirnoT

comment created time in 20 hours

PR closed go-gitea/gitea

Display issue due date as UTC yyyy-mm-dd lgtm/need 2

Previous version did convert to server time zone which was incorrect because the due date is stored as 00:00 utc and it should not be timezone-converted as it may display a different day.

Fixes: https://github.com/go-gitea/gitea/issues/11686

+7 -2

4 comments

2 changed files

silverwind

pr closed time in 20 hours

CommitCommentEvent

created tagsilverwind/versions

tag8.3.1

CLI to flexibly increment a project's version

created time in 2 days

push eventsilverwind/versions

silverwind

commit sha 5581adf0074ebd82e05d3d7ebd554d71ca3928ea

8.3.1 * update help (silverwind)

view details

push time in 2 days

push eventsilverwind/versions

silverwind

commit sha 899c02efe530a3e62c3e6ea76645fe3f1102d248

update help

view details

push time in 2 days

push eventsilverwind/versions

silverwind

commit sha 225bf9d373776ff0c336d231210fef24ce688ee0

8.3.0 * add --globless (silverwind) * tweak example (silverwind) * shorten help more (silverwind) * reduce examples (silverwind)

view details

push time in 2 days

created tagsilverwind/versions

tag8.3.0

CLI to flexibly increment a project's version

created time in 2 days

push eventsilverwind/versions

silverwind

commit sha d13f4fac19b78e902b3024d2c7d1047f2fcde863

add --globless

view details

push time in 2 days

push eventsilverwind/versions

silverwind

commit sha dbb786c5055f228f52f7db54c18287bca17917cb

add --no-glob, rename --gitless and --packageless

view details

push time in 2 days

push eventsilverwind/versions

silverwind

commit sha 25f792d8b0e5456c54d412b17e34bb1b8063b2cf

add --no-glob, rename --gitless and --packageless

view details

push time in 2 days

push eventsilverwind/versions

silverwind

commit sha a59cbfe1670e3fe559291dd4a3c2e335072d95f6

add --no-glob, rename --gitless and --packageless

view details

push time in 2 days

push eventsilverwind/versions

silverwind

commit sha 0568492e959772bdee9ab9063d8f0fb8abe6a175

add --no-glob, rename --gitless and --packageless

view details

push time in 2 days

push eventsilverwind/versions

silverwind

commit sha 72b2642ef2d6490df20d01e77d2af13e5e182a6f

tweak example

view details

push time in 2 days

push eventsilverwind/versions

silverwind

commit sha 8c48cac831f97869790348c893f243c270260b77

shorten help more

view details

push time in 2 days

push eventsilverwind/versions

silverwind

commit sha faabe1e32a2a6f5d9780972866538843998f3332

reduce examples

view details

push time in 2 days

created tagsilverwind/versions

tag8.2.11

CLI to flexibly increment a project's version

created time in 2 days

push eventsilverwind/versions

silverwind

commit sha 96e5dd2e5adc2a586df5f453121f0269aecfbe81

ingore check-ignore exit code

view details

push time in 2 days

push eventsilverwind/versions

silverwind

commit sha 968c12d5b0312e019c3e1602074ba3f5ec70f43c

tweak help

view details

push time in 2 days

push eventsilverwind/versions

silverwind

commit sha b801f585482d8b320a4ce7477f098ab7978a3e02

tweak help

view details

push time in 2 days

push eventsilverwind/versions

silverwind

commit sha d1cd44d1b91dc2462d574005f07904deb537ba5d

update deps, tweaks

view details

push time in 2 days

push eventsilverwind/versions

silverwind

commit sha e2668e3099739d4c298fe572ee4cb10bd116c65e

don't trim stdout as execa does that

view details

push time in 2 days

push eventsilverwind/versions

silverwind

commit sha cf83255b70756adb1fec1918e26498f8ef213f67

don't 'git add' gitignored files, fixes #20

view details

push time in 2 days

issue closedsilverwind/versions

Versions tries to commit package-lock.json if it exists.

This of course fails since package-lock.json is added to the .gitignore file. Removing the file completely allows the npm run patch command to complete successfully.

This was tested on the latest version (8.2.10).

<details><summary>Transcript</summary>

boss@AfroThundr-Edge: ~/Projects/Wikipedia-Dark $  npm run patch

> wikipedia-dark@3.4.1 patch /home/boss/Projects/Wikipedia-Dark
> versions -p -C patch wikipedia-dark.user.css

+ git add wikipedia-dark.user.css package.json package-lock.json
The following paths are ignored by one of your .gitignore files:
package-lock.json
hint: Use -f if you really want to add them.
hint: Turn this message off by running
hint: "git config advice.addIgnoredFile false"
Error: Command failed with exit code 1: git add wikipedia-dark.user.css package.json package-lock.json
The following paths are ignored by one of your .gitignore files:
package-lock.json
hint: Use -f if you really want to add them.
hint: Turn this message off by running
hint: "git config advice.addIgnoredFile false"
    at ge (/home/boss/Projects/Wikipedia-Dark/node_modules/versions/versions:2:14083)
    at /home/boss/Projects/Wikipedia-Dark/node_modules/versions/versions:2:26432
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async ps (/home/boss/Projects/Wikipedia-Dark/node_modules/versions/versions:2:105488)
    at async /home/boss/Projects/Wikipedia-Dark/node_modules/versions/versions:2:108293
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! wikipedia-dark@3.4.1 patch: `versions -p -C patch wikipedia-dark.user.css`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the wikipedia-dark@3.4.1 patch script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/boss/.npm/_logs/2020-05-29T07_10_45_901Z-debug.log
boss@AfroThundr-Edge: ~/Projects/Wikipedia-Dark $  rm package-lock.json 
boss@AfroThundr-Edge: ~/Projects/Wikipedia-Dark $  git status
On branch master
Your branch is ahead of 'origin/master' by 4 commits.
  (use "git push" to publish your local commits)

Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        modified:   package.json
        modified:   wikipedia-dark.user.css

Untracked files:
  (use "git add <file>..." to include in what will be committed)
        TODO.md

boss@AfroThundr-Edge: ~/Projects/Wikipedia-Dark $  git reset --hard HEAD
HEAD is now at 2176fac Updated devDependencies
boss@AfroThundr-Edge: ~/Projects/Wikipedia-Dark $  npm run patch

> wikipedia-dark@3.4.0 patch /home/boss/Projects/Wikipedia-Dark
> versions -p -C patch wikipedia-dark.user.css

+ git add wikipedia-dark.user.css package.json
+ git commit -F -
Please specify how long the signature should be valid.
         0 = signature does not expire
      <n>  = signature expires in n days
      <n>w = signature expires in n weeks
      <n>m = signature expires in n months
      <n>y = signature expires in n years
Signature is valid for? (0) 
Signature does not expire at all
Is this correct? (y/N) y
[master 5c5e5d9] v3.4.1
 2 files changed, 2 insertions(+), 2 deletions(-)
+ git tag -f -F - v3.4.1
Please specify how long the signature should be valid.
         0 = signature does not expire
      <n>  = signature expires in n days
      <n>w = signature expires in n weeks
      <n>m = signature expires in n months
      <n>y = signature expires in n years
Signature is valid for? (0) 
Signature does not expire at all
Is this correct? (y/N) y
boss@AfroThundr-Edge: ~/Projects/Wikipedia-Dark $

</details>

closed time in 2 days

AfroThundr3007730

pull request commentgo-gitea/gitea

Fix align issues and decrease avatar size on PR timeline

Maybe increase the margin between timeline icon and avatar/text slightly. It looks a bit crammed.

CirnoT

comment created time in 2 days

CommitCommentEvent

push eventStylishThemes/GitHub-Dark

silverwind

commit sha f9b3df2e0ee8cf66080b8a4e40a512991ec60090

Add node_modules dependencies to make targets It will no longer be necessary to manually install node_modules.

view details

push time in 2 days

push eventsilverwind/fetch-css

silverwind

commit sha db46e5a7dc6f09b30a6d0096fc29dad7d3f20eea

update ci commands

view details

push time in 2 days

push eventsilverwind/remap-css

silverwind

commit sha 4d9012cb549578c1d534f3d83186a7f860484ea6

update ci commands

view details

push time in 2 days

push eventsilverwind/gitea

silverwind

commit sha 53146f1c42cee76d484281745a37d916d654a4ce

fix utc conversion

view details

push time in 2 days

pull request commentgo-gitea/gitea

Display issue due date as UTC yyyy-mm-dd

This also fixes the inconsitency in due date display so these now match:

image

image

silverwind

comment created time in 2 days

pull request commentgo-gitea/gitea

Change language statistics to save size instead of percentage

Ah, missed that. Carry on.

lafriks

comment created time in 2 days

PR opened go-gitea/gitea

Display issue due date as UTC yyyy-mm-dd

Previous version did convert to local time zone which was incorrect because the due date is stored as 00:00 utc and it should not be timezone-converted as it may display a different day.

Fixes: https://github.com/go-gitea/gitea/issues/11686

+7 -2

0 comment

2 changed files

pr created time in 2 days

create barnchsilverwind/gitea

branch : due

created branch time in 2 days

issue commentgo-gitea/gitea

Issue due date affected by time zone

I guess a better fix is to display the date as UTC (instead of local as right now) while continuing to store 00:00 UTC in the database.

silverwind

comment created time in 2 days

PR closed go-gitea/gitea

Fix issue due date always being UTC lgtm/need 2

Fixes: https://github.com/go-gitea/gitea/issues/11686

Creates a local 00:00 date and toISOString will convert it to UTC. So essentially the exact due time is now always 00:00 in the user's current timezone instead of previously 00:00 UTC.

+1 -3

2 comments

1 changed file

silverwind

pr closed time in 2 days

pull request commentgo-gitea/gitea

Fix issue due date always being UTC

Sounds good from a consitency perspective to have timezone-independent dates on the server, but the display issue on the client (which converts from UTC to local) will remain in that case.

silverwind

comment created time in 2 days

pull request commentgo-gitea/gitea

Change language statistics to save size instead of percentage

You linked https://github.com/go-gitea/gitea/pull/11672 but I fail to see how it's related.

lafriks

comment created time in 2 days

PR opened go-gitea/gitea

Fix issue due date always being UTC

Fixes: https://github.com/go-gitea/gitea/issues/11686

new Date(yyyy-mm-dd 00:00:00) refers to local 00:00 and toISOString will convert it to UTC.

+1 -3

0 comment

1 changed file

pr created time in 2 days

create barnchsilverwind/gitea

branch : fix-due

created branch time in 2 days

pull request commentgo-gitea/gitea

Change language statistics to save size instead of percentage

How does this fix the case of yarn.lock exactly?

lafriks

comment created time in 2 days

issue openedgo-gitea/gitea

Issue due date affected by time zone

Setting a issue due date send a full UTC date due_date: "2020-05-25T00:00:00.000Z" to the backend but depending on the user's time zone, the displayed date may not be 2020-05-25. We should probably remove/ignore the time part or render UTC.

created time in 2 days

pull request commentgo-gitea/gitea

Replace jquery-datetimepicker with native date input

I tried changing it to send yyyy-mm-dd format but the backend rejects that. Definitely a separate issue.

silverwind

comment created time in 2 days

pull request commentgo-gitea/gitea

Replace jquery-datetimepicker with native date input

It's wrongly passing the date to the JS Date contructor.

silverwind

comment created time in 2 days

pull request commentgo-gitea/gitea

Replace jquery-datetimepicker with native date input

Due date also sends with time info so there is a bug there that is not present on milestone.

silverwind

comment created time in 2 days

pull request commentgo-gitea/gitea

Replace jquery-datetimepicker with native date input

Chrome 83 does the right thing:

image

Why is there due_date in your example?

silverwind

comment created time in 2 days

pull request commentgo-gitea/gitea

Replace jquery-datetimepicker with native date input

MDN says:

Value | A DOMString representing a date in YYYY-MM-DD format, or empty

silverwind

comment created time in 2 days

pull request commentgo-gitea/gitea

Replace jquery-datetimepicker with native date input

Is this a Chrome bug? I thought type=date should always send yyyy-mm-dd.

silverwind

comment created time in 2 days

pull request commentgo-gitea/gitea

Replace jquery-datetimepicker with native date input

Weird. I see "2020-05-05" in the POST and on the rendered date afterwards.

silverwind

comment created time in 2 days

issue commentsilverwind/tcpie

Support for UDP protocol

Listening for ICMP responses would require root priviledges and they are likely to be dropped by firewalls. I don't think this is something I want to do.

cardil

comment created time in 2 days

pull request commentgo-gitea/gitea

Replace jquery-datetimepicker with native date input

Works in my end:

image

silverwind

comment created time in 2 days

push eventsilverwind/gitea

silverwind

commit sha 362c25cb6d9ddb685c5b70ee469424175443aae6

Replace jquery-datetimepicker with native date input This removes the jQuery plugin as well as the associated config options. Native input[type=date] does not require a language attribute as it is localized by default, except for the placeholder attribute for which I currently piggy-back the repo.issues.due_date_form localization option. Implementation should pretty much match GH. Of note is that Safari does not provide a UI for this input type, but I don't think providing one is neccessary and GH did not bother either.

view details

push time in 2 days

PR opened go-gitea/gitea

Replace jquery-datetimepicker with native date input

This removes the jQuery plugin as well as the associated config options. Native input[type=date] does not require a language attribute as it is localized by default, except for the placeholder attribute for which I currently piggy-back the repo.issues.due_date_form localization option.

Implementation should pretty much match GH. Of note is that Safari does not provide a UI for this input type, but I don't think providing one is neccessary and GH did not bother either.

Before: image

After: image

+7 -227

0 comment

17 changed files

pr created time in 2 days

push eventsilverwind/gitea

silverwind

commit sha 508835d55b6844addfea381526d0103687ef2bb4

Replace jquery-datetimepicker with native date input This removes the jQuery plugin as well as the associated config options. Native input[type=date] does not require a language attribute as it is localized by default, except for the placeholder attribute for which I currently piggy-back the repo.issues.due_date_form localization option. Implementation should pretty much match GH. Of note is that Safari does not provide a UI for this input type, but I don't think providing one is neccessary and GH did not bother either.

view details

push time in 2 days

push eventsilverwind/gitea

silverwind

commit sha ffeb43a5bf2b5bb0243a7ea6eb8dab2a09ff335e

Replace jquery-datetimepicker with native date input This removes the jQuery plugin as well as the associated config options. Native input[type=date] does not require a language attribute as it is localized by default, except for the placeholder attribute for which I currently piggy-back the repo.issues.due_date_form localization option. Implementation should pretty much match GH. Of note is that Safari does not provide a UI for this input type, but I don't think providing one is neccessary and GH did not bother either.

view details

push time in 2 days

create barnchsilverwind/gitea

branch : datetime

created branch time in 2 days

issue closedsilverwind/tcpie

Support for UDP protocol

Tcpie is nice tool. Sometimes it might be useful to use UDP instead of tcp.

closed time in 2 days

cardil

issue commentsilverwind/tcpie

Support for UDP protocol

Not possible. UDP does not handshake and to get a UDP service to send something back you need to send it application-specific data which one can't generate without implementing those protocols.

cardil

comment created time in 2 days

Pull request review commentgo-gitea/gitea

Exclude certain languages from repo stats

 import (  const fileSizeLimit int64 = 16 * 1024 * 1024 +// specialLanguages defines list of languages that are excluded from calculation+// unless they are the only language present in repository
// specialLanguages defines list of languages that are excluded from the calculation
// unless they are the only language present in repository. Only languages which under
// normal circumstances should not be considered to be code should be listed here.
CirnoT

comment created time in 2 days

pull request commentgo-gitea/gitea

Exclude certain languages from repo stats

Ok, I guess the notion behind this that these files would never represent source code. Certainly not true for YAML or SVG but those are kind of grey areas.

BTW, yarn lockfile v1 is not strictly YAML format, only the v2 version is. Still most mechanisms seem to pick it up as YAML for some reason.

CirnoT

comment created time in 2 days

push eventsilverwind/ansible-examples

silverwind

commit sha ba3d8afd46690ffd50a3e6f4373aeae773235313

reclassify yaml

view details

push time in 2 days

fork silverwind/ansible-examples

A few starter examples of ansible playbooks, to show features and how they work together. See http://galaxy.ansible.com for example roles from the Ansible community for deploying many popular applications.

fork in 2 days

pull request commentgo-gitea/gitea

Exclude certain languages from repo stats

So you're saying this exclusion is not part of linguist but some hackery that GitHub does after the files were processed by linuist?

I wonder if one can overrule this via gitattributes *.yaml -linguist-vendored -linguist-generated.

Maybe instead of a plain exclusion list, we want to specify the files as generated so enry will see them as such, it'd be more compatible and user-overridable.

CirnoT

comment created time in 2 days

pull request commentgo-gitea/gitea

Exclude certain languages from repo stats

What I worry thought is that let's say I have a repo for a Ansible role. These are almost purely YAML and those files are basically equivalent to code. If I introduce a bash script into said repo, it would no longer count any YAML at all?

Maybe some sort of filename-based approach would be better and for that we can mostly lean on enry/linguist, right?

CirnoT

comment created time in 2 days

pull request commentgo-gitea/gitea

Exclude certain languages from repo stats

Maybe add a comment describing that the reason for the existance of this list is to overrule linguist/enry's behaviour that is considered suboptimal.

CirnoT

comment created time in 2 days

pull request commentgo-gitea/gitea

Exclude certain languages from repo stats

I'd definitely agree that yarn.lock should be considered generated and it just seems silly to not do it for yarn.lock but do so for package-lock.json.

The argument that yaml is easier to diff than json is also silly, I can easily visually diff both for small changes and for bigger ones I skip over both of them.

CirnoT

comment created time in 2 days

issue commentsilverwind/versions

Versions tries to commit package-lock.json if it exists.

Or maybe it'd be better to never touch package-lock.json to begin with. The version field in there has no real significance to my understanding.

AfroThundr3007730

comment created time in 2 days

pull request commentgo-gitea/gitea

Exclude certain languages from repo stats

I wonder if this should be better done upstream in go-enry.

CirnoT

comment created time in 2 days

pull request commentgo-gitea/gitea

load U2F js only on pages which need it

Maybe @6543 can test this? I don't have a security token, so I can't verify.

kdomanski

comment created time in 2 days

pull request commentgo-gitea/gitea

load U2F js only on pages which need it

Not sure I understand the impact of the move of this variable.

Is theU2FRegistrations variable not required in the new context?

kdomanski

comment created time in 2 days

issue commentsilverwind/versions

Versions tries to commit package-lock.json if it exists.

Probably need to use https://git-scm.com/docs/git-check-ignore before adding any files.

AfroThundr3007730

comment created time in 2 days

issue commentStylishThemes/GitHub-Dark

Search field not properly styled when focused while logged out

Would not call it broken, the style is close to the original, except inverted colors. The border is present on original too.

LingMan

comment created time in 2 days

created tagStylishThemes/GitHub-Dark

tagv2.0.95

:octocat: Dark GitHub style

created time in 2 days

push eventStylishThemes/GitHub-Dark

github-actions[bot]

commit sha 532760c9fe90c099e3a5d67817ab2ddf9420977e

automated regeneration

view details

github-actions[bot]

commit sha d680498631d5e6b36fa9b4e5b7c2ab977bab01cd

v2.0.95 * automated regeneration (github-actions[bot])

view details

push time in 2 days

delete branch silverwind/gitea

delete branch : backport-11526-111

delete time in 3 days

push eventStylishThemes/GitHub-Dark

github-actions[bot]

commit sha 376815e89b3ba7a4733fd2a77099e2ed765cb4e3

automated regeneration

view details

github-actions[bot]

commit sha 3b65d2089cd81f4601344ada6259be080cb37a4c

v2.0.94 * automated regeneration (github-actions[bot])

view details

push time in 3 days

created tagStylishThemes/GitHub-Dark

tagv2.0.94

:octocat: Dark GitHub style

created time in 3 days

created tagStylishThemes/GitHub-Dark

tagv2.0.93

:octocat: Dark GitHub style

created time in 3 days

push eventStylishThemes/GitHub-Dark

silverwind

commit sha b9ccefb7abedbfd563dd035ce8b1553ae71bd272

v2.0.93 * color tweaks and add a few more rules (silverwind) * remove manual pagination styling (silverwind) * add background to labels/milestone buttons (silverwind)

view details

push time in 3 days

issue commentgo-gitea/gitea

[Feature] support disable repository programing language Detection

Should be per-repo. I think supporting the linguist gitattributes is probably a good idea which probably makes this an upstream issue.

ddatsh

comment created time in 3 days

push eventStylishThemes/GitHub-Dark

silverwind

commit sha cb13c254dce4961a4f6714d97d20dceb1437779c

color tweaks and add a few more rules

view details

push time in 3 days

pull request commentyury-dymov/react-autocomplete-input

Use PropTypes.elementType to support wrapped components

@yury-dymov any chance to see this merged? I want to stop using my fork :)

silverwind

comment created time in 3 days

push eventsilverwind/rrdir

silverwind

commit sha 145fcdcb3d36a0036b95fa18459b5a06dfbfe1d4

add deps target

view details

push time in 3 days

pull request commentgo-gitea/gitea

Exclude generated files from language statistics

I wonder if there is a relatively cheap way of using isGenerated on our diff pages.

Seconding this, auto-collapsing generated files in diffs would indeed be a nice feature.

lafriks

comment created time in 3 days

pull request commentreact-dnd/react-dnd

v11.1.2

Did this publish? npm shows only 11.1.1.

darthtrevino

comment created time in 3 days

created tagsilverwind/tcpie

tag9.0.1

CLI tool to ping any TCP port

created time in 4 days

push eventsilverwind/tcpie

silverwind

commit sha aecd27a3ce4bed26d92a51752665353c416cbec8

update deps

view details

silverwind

commit sha 9e2f22a84b1a1fa6c10714d8bb4026d58c291271

9.0.1 * update deps (silverwind) * test node 14 (silverwind)

view details

push time in 4 days

push eventStylishThemes/GitHub-Dark

silverwind

commit sha beb7a85fc6560d5513283160deed10fc321aea2f

remove manual pagination styling

view details

push time in 4 days

push eventStylishThemes/GitHub-Dark

silverwind

commit sha c909c8b265b2654cb059a45119d076900d5d410f

add background to labels/milestone buttons

view details

push time in 4 days

Pull request review commentgo-gitea/gitea

Fix message wrapping on PR commit list

 			{{else}} 				<span class="{{$class}}"> 			{{end}}-					<span class="shortsha">{{ShortSha .ID.String}}</span>+			<span class="shortsha">{{ShortSha .ID.String}}</span> 			{{if $.Issue.PullRequest.BaseRepo.Name}} 				</a> 			{{else}} 				</span> 			{{end}} 		</span> -		<span class="message-wrapper">-			{{ $commitLink:= printf "%s/%s/%s/commit/%s" AppSubUrl  $.Issue.PullRequest.BaseRepo.OwnerName $.Issue.PullRequest.BaseRepo.Name .ID }}-			<span class="mono commit-summary has-emoji{{if gt .ParentCount 1}} grey text{{end}}" title="{{.Summary}}">{{RenderCommitMessageLinkSubject .Message ($.Issue.PullRequest.BaseRepo.Link|Escape) $commitLink $.Issue.PullRequest.BaseRepo.ComposeMetas}}</span>-		</span>+		{{ $commitLink:= printf "%s/%s/%s/commit/%s" AppSubUrl  $.Issue.PullRequest.BaseRepo.OwnerName $.Issue.PullRequest.BaseRepo.Name .ID }}+		<span class="mono commit-summary has-emoji{{if gt .ParentCount 1}} grey text{{end}}" title="{{.Summary}}">{{RenderCommitMessageLinkSubject .Message ($.Issue.PullRequest.BaseRepo.Link|Escape) $commitLink $.Issue.PullRequest.BaseRepo.ComposeMetas}}</span>
		<span class="mono commit-summary {{if gt .ParentCount 1}} grey text{{end}}" title="{{.Summary}}">{{RenderCommitMessageLinkSubject .Message ($.Issue.PullRequest.BaseRepo.Link|Escape) $commitLink $.Issue.PullRequest.BaseRepo.ComposeMetas}}</span>

Might as well remove this unused class here (was previously used by JS emoji conversion). This looks to be the last occurence in the codebase.

CirnoT

comment created time in 4 days

pull request commentgo-gitea/gitea

Narrow down Edge version in browser support docs

Looks weird

I think it's fine. "Edge (Chromium and EdgeHTML)" would less clear.

silverwind

comment created time in 4 days

issue commentStylishThemes/GitHub-Dark

New version of octicons is being used on the site now

There are a few more SVG's used in background on off-sites like developer, but main site is fine. We should remove all of them and style the original icons via fill if possible.

xt0rted

comment created time in 4 days

push eventStylishThemes/GitHub-Dark

silverwind

commit sha 8cb13d833f9f414b5a74ee8525977ba05088ae59

v2.0.92 * brighten tab hover color (silverwind) * remove some potentially unneeded svgs - #1117 (silverwind) * remove padding hacks on repo and page tabs (silverwind) * remove hsla's from generator, they are pointless rules (silverwind) * fix mobile site header color opacities (silverwind)

view details

push time in 4 days

created tagStylishThemes/GitHub-Dark

tagv2.0.92

:octocat: Dark GitHub style

created time in 4 days

more