refactor repo

This commit is contained in:
PomPom 2024-03-14 10:10:45 +01:00
parent c790f6fedd
commit 027f62ea0d
206 changed files with 7407 additions and 1 deletions

View File

@ -0,0 +1,4 @@
# gitea public key
command="/usr/local/bin/gitea --config=/data/gitea/conf/app.ini serv key-1",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty,no-user-rc,restrict ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAZgYIkf7FlB4A3GXlgqQLTrtQnCbqOWwEiE+L0mm+ll pauline@srifi.fr
# gitea public key
command="/usr/local/bin/gitea --config=/data/gitea/conf/app.ini serv key-2",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty,no-user-rc,restrict ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDGkt8ePQZ0yC0uQSMgrg7CEzJPl9n8apwNECp8+yv9DNrwgXhFCgdnMnqxS8aaU2x7sAjTc5E251t9zc+DeUKeA3EDZsquBKQeEshPYVvOf7r5S5lgj2MInBotebz6a00WKnb2w/buJE9n32EQPUjU5WQqOhi27pVGa1M4d7R0Dlbxr0UYNzFQpEb/z/VpI2nxhDfEOx2pXYW5p0JQW+uxe7c1uTXQ0DIFpnxfGAOW6NkMYmmgqG8VZxWPoIsW0tW/+mlxW4toeOH5BiRU3jZ9ZV5/mlX0ELNoHCt57Q9tSdEEJkFEJ7BA4IRSdYJfjgufi6iw9R8be59YDfJ0GAWyL5A95kPL6ISI8TG2ak0APoYlhjfYIZAbrVXauPLMf1Cw6uz/5WT1GBBbz2+JvQQq3cR0z9+N21Giz5Za36fEpEEJihBScEwJ+8fUADXytWY1/trBq2kaIwjvi0fl/0dZ526Wru8hzi/t98tVsuxMT7J3+jSRsVOsTeqThdNYDf/r3GxjD4aQa0gyN9ZllMAwUJJNTgHSnWxXksYzlfEmxrbgEjNQUZlFHbZjkUae7xdjQ5QqxuoqTRbtnQZpoIh9/sQ5flQQ9UpUFoYFlBkyRKMZlb1FPW4+WLthNjgat3nDbw9P9r7tNebb1NmGH2v9zMpmBwK25anNg7GY52hhkw== paulinesrifi@MacBook-Pro-de-Pauline.local

View File

@ -0,0 +1 @@
GITEA_CUSTOM=/data/gitea

View File

@ -0,0 +1 @@
ref: refs/heads/main

View File

@ -0,0 +1,5 @@
[core]
repositoryformatversion = 0
filemode = true
bare = true
ignorecase = true

View File

@ -0,0 +1 @@
Unnamed repository; edit this file 'description' to name the repository.

View File

@ -0,0 +1,15 @@
#!/bin/sh
#
# An example hook script to check the commit log message taken by
# applypatch from an e-mail message.
#
# The hook should exit with non-zero status after issuing an
# appropriate message if it wants to stop the commit. The hook is
# allowed to edit the commit message file.
#
# To enable this hook, rename this file to "applypatch-msg".
. git-sh-setup
commitmsg="$(git rev-parse --git-path hooks/commit-msg)"
test -x "$commitmsg" && exec "$commitmsg" ${1+"$@"}
:

View File

@ -0,0 +1,24 @@
#!/bin/sh
#
# An example hook script to check the commit log message.
# Called by "git commit" with one argument, the name of the file
# that has the commit message. The hook should exit with non-zero
# status after issuing an appropriate message if it wants to stop the
# commit. The hook is allowed to edit the commit message file.
#
# To enable this hook, rename this file to "commit-msg".
# Uncomment the below to add a Signed-off-by line to the message.
# Doing this in a hook is a bad idea in general, but the prepare-commit-msg
# hook is more suited to it.
#
# SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
# grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"
# This example catches duplicate Signed-off-by lines.
test "" = "$(grep '^Signed-off-by: ' "$1" |
sort | uniq -c | sed -e '/^[ ]*1[ ]/d')" || {
echo >&2 Duplicate Signed-off-by lines.
exit 1
}

View File

@ -0,0 +1,16 @@
#!/usr/bin/env bash
# AUTO GENERATED BY GITEA, DO NOT MODIFY
data=$(cat)
exitcodes=""
hookname=$(basename $0)
GIT_DIR=${GIT_DIR:-$(dirname $0)/..}
for hook in ${GIT_DIR}/hooks/${hookname}.d/*; do
test -x "${hook}" && test -f "${hook}" || continue
echo "${data}" | "${hook}"
exitcodes="${exitcodes} $?"
done
for i in ${exitcodes}; do
[ ${i} -eq 0 ] || exit ${i}
done

View File

@ -0,0 +1,3 @@
#!/usr/bin/env bash
# AUTO GENERATED BY GITEA, DO NOT MODIFY
/usr/local/bin/gitea hook --config=/data/gitea/conf/app.ini post-receive

View File

@ -0,0 +1,8 @@
#!/bin/sh
#
# An example hook script to prepare a packed repository for use over
# dumb transports.
#
# To enable this hook, rename this file to "post-update".
exec git update-server-info

View File

@ -0,0 +1,14 @@
#!/bin/sh
#
# An example hook script to verify what is about to be committed
# by applypatch from an e-mail message.
#
# The hook should exit with non-zero status after issuing an
# appropriate message if it wants to stop the commit.
#
# To enable this hook, rename this file to "pre-applypatch".
. git-sh-setup
precommit="$(git rev-parse --git-path hooks/pre-commit)"
test -x "$precommit" && exec "$precommit" ${1+"$@"}
:

View File

@ -0,0 +1,49 @@
#!/bin/sh
#
# An example hook script to verify what is about to be committed.
# Called by "git commit" with no arguments. The hook should
# exit with non-zero status after issuing an appropriate message if
# it wants to stop the commit.
#
# To enable this hook, rename this file to "pre-commit".
if git rev-parse --verify HEAD >/dev/null 2>&1
then
against=HEAD
else
# Initial commit: diff against an empty tree object
against=$(git hash-object -t tree /dev/null)
fi
# If you want to allow non-ASCII filenames set this variable to true.
allownonascii=$(git config --type=bool hooks.allownonascii)
# Redirect output to stderr.
exec 1>&2
# Cross platform projects tend to avoid non-ASCII filenames; prevent
# them from being added to the repository. We exploit the fact that the
# printable range starts at the space character and ends with tilde.
if [ "$allownonascii" != "true" ] &&
# Note that the use of brackets around a tr range is ok here, (it's
# even required, for portability to Solaris 10's /usr/bin/tr), since
# the square bracket bytes happen to fall in the designated range.
test $(git diff --cached --name-only --diff-filter=A -z $against |
LC_ALL=C tr -d '[ -~]\0' | wc -c) != 0
then
cat <<\EOF
Error: Attempt to add a non-ASCII file name.
This can cause problems if you want to work with people on other platforms.
To be portable it is advisable to rename the file.
If you know what you are doing you can disable this check using:
git config hooks.allownonascii true
EOF
exit 1
fi
# If there are whitespace errors, print the offending file names and fail.
exec git diff-index --check --cached $against --

View File

@ -0,0 +1,13 @@
#!/bin/sh
#
# An example hook script to verify what is about to be committed.
# Called by "git merge" with no arguments. The hook should
# exit with non-zero status after issuing an appropriate message to
# stderr if it wants to stop the merge commit.
#
# To enable this hook, rename this file to "pre-merge-commit".
. git-sh-setup
test -x "$GIT_DIR/hooks/pre-commit" &&
exec "$GIT_DIR/hooks/pre-commit"
:

View File

@ -0,0 +1,53 @@
#!/bin/sh
# An example hook script to verify what is about to be pushed. Called by "git
# push" after it has checked the remote status, but before anything has been
# pushed. If this script exits with a non-zero status nothing will be pushed.
#
# This hook is called with the following parameters:
#
# $1 -- Name of the remote to which the push is being done
# $2 -- URL to which the push is being done
#
# If pushing without using a named remote those arguments will be equal.
#
# Information about the commits which are being pushed is supplied as lines to
# the standard input in the form:
#
# <local ref> <local oid> <remote ref> <remote oid>
#
# This sample shows how to prevent push of commits where the log message starts
# with "WIP" (work in progress).
remote="$1"
url="$2"
zero=$(git hash-object --stdin </dev/null | tr '[0-9a-f]' '0')
while read local_ref local_oid remote_ref remote_oid
do
if test "$local_oid" = "$zero"
then
# Handle delete
:
else
if test "$remote_oid" = "$zero"
then
# New branch, examine all commits
range="$local_oid"
else
# Update to existing branch, examine new commits
range="$remote_oid..$local_oid"
fi
# Check for WIP commit
commit=$(git rev-list -n 1 --grep '^WIP' "$range")
if test -n "$commit"
then
echo >&2 "Found WIP commit in $local_ref, not pushing"
exit 1
fi
fi
done
exit 0

View File

@ -0,0 +1,169 @@
#!/bin/sh
#
# Copyright (c) 2006, 2008 Junio C Hamano
#
# The "pre-rebase" hook is run just before "git rebase" starts doing
# its job, and can prevent the command from running by exiting with
# non-zero status.
#
# The hook is called with the following parameters:
#
# $1 -- the upstream the series was forked from.
# $2 -- the branch being rebased (or empty when rebasing the current branch).
#
# This sample shows how to prevent topic branches that are already
# merged to 'next' branch from getting rebased, because allowing it
# would result in rebasing already published history.
publish=next
basebranch="$1"
if test "$#" = 2
then
topic="refs/heads/$2"
else
topic=`git symbolic-ref HEAD` ||
exit 0 ;# we do not interrupt rebasing detached HEAD
fi
case "$topic" in
refs/heads/??/*)
;;
*)
exit 0 ;# we do not interrupt others.
;;
esac
# Now we are dealing with a topic branch being rebased
# on top of master. Is it OK to rebase it?
# Does the topic really exist?
git show-ref -q "$topic" || {
echo >&2 "No such branch $topic"
exit 1
}
# Is topic fully merged to master?
not_in_master=`git rev-list --pretty=oneline ^master "$topic"`
if test -z "$not_in_master"
then
echo >&2 "$topic is fully merged to master; better remove it."
exit 1 ;# we could allow it, but there is no point.
fi
# Is topic ever merged to next? If so you should not be rebasing it.
only_next_1=`git rev-list ^master "^$topic" ${publish} | sort`
only_next_2=`git rev-list ^master ${publish} | sort`
if test "$only_next_1" = "$only_next_2"
then
not_in_topic=`git rev-list "^$topic" master`
if test -z "$not_in_topic"
then
echo >&2 "$topic is already up to date with master"
exit 1 ;# we could allow it, but there is no point.
else
exit 0
fi
else
not_in_next=`git rev-list --pretty=oneline ^${publish} "$topic"`
/usr/bin/perl -e '
my $topic = $ARGV[0];
my $msg = "* $topic has commits already merged to public branch:\n";
my (%not_in_next) = map {
/^([0-9a-f]+) /;
($1 => 1);
} split(/\n/, $ARGV[1]);
for my $elem (map {
/^([0-9a-f]+) (.*)$/;
[$1 => $2];
} split(/\n/, $ARGV[2])) {
if (!exists $not_in_next{$elem->[0]}) {
if ($msg) {
print STDERR $msg;
undef $msg;
}
print STDERR " $elem->[1]\n";
}
}
' "$topic" "$not_in_next" "$not_in_master"
exit 1
fi
<<\DOC_END
This sample hook safeguards topic branches that have been
published from being rewound.
The workflow assumed here is:
* Once a topic branch forks from "master", "master" is never
merged into it again (either directly or indirectly).
* Once a topic branch is fully cooked and merged into "master",
it is deleted. If you need to build on top of it to correct
earlier mistakes, a new topic branch is created by forking at
the tip of the "master". This is not strictly necessary, but
it makes it easier to keep your history simple.
* Whenever you need to test or publish your changes to topic
branches, merge them into "next" branch.
The script, being an example, hardcodes the publish branch name
to be "next", but it is trivial to make it configurable via
$GIT_DIR/config mechanism.
With this workflow, you would want to know:
(1) ... if a topic branch has ever been merged to "next". Young
topic branches can have stupid mistakes you would rather
clean up before publishing, and things that have not been
merged into other branches can be easily rebased without
affecting other people. But once it is published, you would
not want to rewind it.
(2) ... if a topic branch has been fully merged to "master".
Then you can delete it. More importantly, you should not
build on top of it -- other people may already want to
change things related to the topic as patches against your
"master", so if you need further changes, it is better to
fork the topic (perhaps with the same name) afresh from the
tip of "master".
Let's look at this example:
o---o---o---o---o---o---o---o---o---o "next"
/ / / /
/ a---a---b A / /
/ / / /
/ / c---c---c---c B /
/ / / \ /
/ / / b---b C \ /
/ / / / \ /
---o---o---o---o---o---o---o---o---o---o---o "master"
A, B and C are topic branches.
* A has one fix since it was merged up to "next".
* B has finished. It has been fully merged up to "master" and "next",
and is ready to be deleted.
* C has not merged to "next" at all.
We would want to allow C to be rebased, refuse A, and encourage
B to be deleted.
To compute (1):
git rev-list ^master ^topic next
git rev-list ^master next
if these match, topic has not merged in next at all.
To compute (2):
git rev-list master..topic
if this is empty, it is fully merged to "master".
DOC_END

View File

@ -0,0 +1,16 @@
#!/usr/bin/env bash
# AUTO GENERATED BY GITEA, DO NOT MODIFY
data=$(cat)
exitcodes=""
hookname=$(basename $0)
GIT_DIR=${GIT_DIR:-$(dirname $0)/..}
for hook in ${GIT_DIR}/hooks/${hookname}.d/*; do
test -x "${hook}" && test -f "${hook}" || continue
echo "${data}" | "${hook}"
exitcodes="${exitcodes} $?"
done
for i in ${exitcodes}; do
[ ${i} -eq 0 ] || exit ${i}
done

View File

@ -0,0 +1,3 @@
#!/usr/bin/env bash
# AUTO GENERATED BY GITEA, DO NOT MODIFY
/usr/local/bin/gitea hook --config=/data/gitea/conf/app.ini pre-receive

View File

@ -0,0 +1,24 @@
#!/bin/sh
#
# An example hook script to make use of push options.
# The example simply echoes all push options that start with 'echoback='
# and rejects all pushes when the "reject" push option is used.
#
# To enable this hook, rename this file to "pre-receive".
if test -n "$GIT_PUSH_OPTION_COUNT"
then
i=0
while test "$i" -lt "$GIT_PUSH_OPTION_COUNT"
do
eval "value=\$GIT_PUSH_OPTION_$i"
case "$value" in
echoback=*)
echo "echo from the pre-receive-hook: ${value#*=}" >&2
;;
reject)
exit 1
esac
i=$((i + 1))
done
fi

View File

@ -0,0 +1,42 @@
#!/bin/sh
#
# An example hook script to prepare the commit log message.
# Called by "git commit" with the name of the file that has the
# commit message, followed by the description of the commit
# message's source. The hook's purpose is to edit the commit
# message file. If the hook fails with a non-zero status,
# the commit is aborted.
#
# To enable this hook, rename this file to "prepare-commit-msg".
# This hook includes three examples. The first one removes the
# "# Please enter the commit message..." help message.
#
# The second includes the output of "git diff --name-status -r"
# into the message, just before the "git status" output. It is
# commented because it doesn't cope with --amend or with squashed
# commits.
#
# The third example adds a Signed-off-by line to the message, that can
# still be edited. This is rarely a good idea.
COMMIT_MSG_FILE=$1
COMMIT_SOURCE=$2
SHA1=$3
/usr/bin/perl -i.bak -ne 'print unless(m/^. Please enter the commit message/..m/^#$/)' "$COMMIT_MSG_FILE"
# case "$COMMIT_SOURCE,$SHA1" in
# ,|template,)
# /usr/bin/perl -i.bak -pe '
# print "\n" . `git diff --cached --name-status -r`
# if /^#/ && $first++ == 0' "$COMMIT_MSG_FILE" ;;
# *) ;;
# esac
# SOB=$(git var GIT_COMMITTER_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
# git interpret-trailers --in-place --trailer "$SOB" "$COMMIT_MSG_FILE"
# if test -z "$COMMIT_SOURCE"
# then
# /usr/bin/perl -i.bak -pe 'print "\n" if !$first_line++' "$COMMIT_MSG_FILE"
# fi

View File

@ -0,0 +1,3 @@
#!/usr/bin/env bash
# AUTO GENERATED BY GITEA, DO NOT MODIFY
/usr/local/bin/gitea hook --config=/data/gitea/conf/app.ini proc-receive

View File

@ -0,0 +1,78 @@
#!/bin/sh
# An example hook script to update a checked-out tree on a git push.
#
# This hook is invoked by git-receive-pack(1) when it reacts to git
# push and updates reference(s) in its repository, and when the push
# tries to update the branch that is currently checked out and the
# receive.denyCurrentBranch configuration variable is set to
# updateInstead.
#
# By default, such a push is refused if the working tree and the index
# of the remote repository has any difference from the currently
# checked out commit; when both the working tree and the index match
# the current commit, they are updated to match the newly pushed tip
# of the branch. This hook is to be used to override the default
# behaviour; however the code below reimplements the default behaviour
# as a starting point for convenient modification.
#
# The hook receives the commit with which the tip of the current
# branch is going to be updated:
commit=$1
# It can exit with a non-zero status to refuse the push (when it does
# so, it must not modify the index or the working tree).
die () {
echo >&2 "$*"
exit 1
}
# Or it can make any necessary changes to the working tree and to the
# index to bring them to the desired state when the tip of the current
# branch is updated to the new commit, and exit with a zero status.
#
# For example, the hook can simply run git read-tree -u -m HEAD "$1"
# in order to emulate git fetch that is run in the reverse direction
# with git push, as the two-tree form of git read-tree -u -m is
# essentially the same as git switch or git checkout that switches
# branches while keeping the local changes in the working tree that do
# not interfere with the difference between the branches.
# The below is a more-or-less exact translation to shell of the C code
# for the default behaviour for git's push-to-checkout hook defined in
# the push_to_deploy() function in builtin/receive-pack.c.
#
# Note that the hook will be executed from the repository directory,
# not from the working tree, so if you want to perform operations on
# the working tree, you will have to adapt your code accordingly, e.g.
# by adding "cd .." or using relative paths.
if ! git update-index -q --ignore-submodules --refresh
then
die "Up-to-date check failed"
fi
if ! git diff-files --quiet --ignore-submodules --
then
die "Working directory has unstaged changes"
fi
# This is a rough translation of:
#
# head_has_history() ? "HEAD" : EMPTY_TREE_SHA1_HEX
if git cat-file -e HEAD 2>/dev/null
then
head=HEAD
else
head=$(git hash-object -t tree --stdin </dev/null)
fi
if ! git diff-index --quiet --cached --ignore-submodules $head --
then
die "Working directory has staged changes"
fi
if ! git read-tree -u -m "$commit"
then
die "Could not update working tree to new HEAD"
fi

View File

@ -0,0 +1,15 @@
#!/usr/bin/env bash
# AUTO GENERATED BY GITEA, DO NOT MODIFY
exitcodes=""
hookname=$(basename $0)
GIT_DIR=${GIT_DIR:-$(dirname $0/..)}
for hook in ${GIT_DIR}/hooks/${hookname}.d/*; do
test -x "${hook}" && test -f "${hook}" || continue
"${hook}" $1 $2 $3
exitcodes="${exitcodes} $?"
done
for i in ${exitcodes}; do
[ ${i} -eq 0 ] || exit ${i}
done

View File

@ -0,0 +1,3 @@
#!/usr/bin/env bash
# AUTO GENERATED BY GITEA, DO NOT MODIFY
/usr/local/bin/gitea hook --config=/data/gitea/conf/app.ini update $1 $2 $3

View File

@ -0,0 +1,128 @@
#!/bin/sh
#
# An example hook script to block unannotated tags from entering.
# Called by "git receive-pack" with arguments: refname sha1-old sha1-new
#
# To enable this hook, rename this file to "update".
#
# Config
# ------
# hooks.allowunannotated
# This boolean sets whether unannotated tags will be allowed into the
# repository. By default they won't be.
# hooks.allowdeletetag
# This boolean sets whether deleting tags will be allowed in the
# repository. By default they won't be.
# hooks.allowmodifytag
# This boolean sets whether a tag may be modified after creation. By default
# it won't be.
# hooks.allowdeletebranch
# This boolean sets whether deleting branches will be allowed in the
# repository. By default they won't be.
# hooks.denycreatebranch
# This boolean sets whether remotely creating branches will be denied
# in the repository. By default this is allowed.
#
# --- Command line
refname="$1"
oldrev="$2"
newrev="$3"
# --- Safety check
if [ -z "$GIT_DIR" ]; then
echo "Don't run this script from the command line." >&2
echo " (if you want, you could supply GIT_DIR then run" >&2
echo " $0 <ref> <oldrev> <newrev>)" >&2
exit 1
fi
if [ -z "$refname" -o -z "$oldrev" -o -z "$newrev" ]; then
echo "usage: $0 <ref> <oldrev> <newrev>" >&2
exit 1
fi
# --- Config
allowunannotated=$(git config --type=bool hooks.allowunannotated)
allowdeletebranch=$(git config --type=bool hooks.allowdeletebranch)
denycreatebranch=$(git config --type=bool hooks.denycreatebranch)
allowdeletetag=$(git config --type=bool hooks.allowdeletetag)
allowmodifytag=$(git config --type=bool hooks.allowmodifytag)
# check for no description
projectdesc=$(sed -e '1q' "$GIT_DIR/description")
case "$projectdesc" in
"Unnamed repository"* | "")
echo "*** Project description file hasn't been set" >&2
exit 1
;;
esac
# --- Check types
# if $newrev is 0000...0000, it's a commit to delete a ref.
zero=$(git hash-object --stdin </dev/null | tr '[0-9a-f]' '0')
if [ "$newrev" = "$zero" ]; then
newrev_type=delete
else
newrev_type=$(git cat-file -t $newrev)
fi
case "$refname","$newrev_type" in
refs/tags/*,commit)
# un-annotated tag
short_refname=${refname##refs/tags/}
if [ "$allowunannotated" != "true" ]; then
echo "*** The un-annotated tag, $short_refname, is not allowed in this repository" >&2
echo "*** Use 'git tag [ -a | -s ]' for tags you want to propagate." >&2
exit 1
fi
;;
refs/tags/*,delete)
# delete tag
if [ "$allowdeletetag" != "true" ]; then
echo "*** Deleting a tag is not allowed in this repository" >&2
exit 1
fi
;;
refs/tags/*,tag)
# annotated tag
if [ "$allowmodifytag" != "true" ] && git rev-parse $refname > /dev/null 2>&1
then
echo "*** Tag '$refname' already exists." >&2
echo "*** Modifying a tag is not allowed in this repository." >&2
exit 1
fi
;;
refs/heads/*,commit)
# branch
if [ "$oldrev" = "$zero" -a "$denycreatebranch" = "true" ]; then
echo "*** Creating a branch is not allowed in this repository" >&2
exit 1
fi
;;
refs/heads/*,delete)
# delete branch
if [ "$allowdeletebranch" != "true" ]; then
echo "*** Deleting a branch is not allowed in this repository" >&2
exit 1
fi
;;
refs/remotes/*,commit)
# tracking branch
;;
refs/remotes/*,delete)
# delete tracking branch
if [ "$allowdeletebranch" != "true" ]; then
echo "*** Deleting a tracking branch is not allowed in this repository" >&2
exit 1
fi
;;
*)
# Anything else (is there anything else?)
echo "*** Update hook: unknown type of update to ref $refname of type $newrev_type" >&2
exit 1
;;
esac
# --- Finished
exit 0

View File

@ -0,0 +1,6 @@
# git ls-files --others --exclude-from=.git/info/exclude
# Lines that start with '#' are comments.
# For a project mostly in C, the following would be a good set of
# exclude patterns (uncomment them if you want to use them):
# *.[oa]
# *~

View File

@ -0,0 +1,3 @@
807da2538b9797e3880202f559bd6858a62d3e7d refs/heads/feature-10
16a607b4e427dee7a8814949607784e1e56e749e refs/heads/main
807da2538b9797e3880202f559bd6858a62d3e7d refs/pull/1/head

View File

@ -0,0 +1,15 @@
0000000000000000000000000000000000000000 6f08a05dcd41f7014b817fbf8d91f1b423401886 Gitea <gitea@fake.local> 1707398060 +0100 push
6f08a05dcd41f7014b817fbf8d91f1b423401886 7d89efc1909dcf24b64344fc91715a0f9195fd70 Gitea <gitea@fake.local> 1707398427 +0100 push
7d89efc1909dcf24b64344fc91715a0f9195fd70 5b65ea2912c029f55e229345710b995f1e35a9f6 Gitea <gitea@fake.local> 1707993397 +0100 push
5b65ea2912c029f55e229345710b995f1e35a9f6 20ed8ca88312f56f0623cd66ddfa070fa6a2223b Gitea <gitea@fake.local> 1707993833 +0100 push
20ed8ca88312f56f0623cd66ddfa070fa6a2223b eb18ba1ff45c3c588390744527f439060676d69a Pom <pauline@srifi.fr> 1708006008 +0100 push
eb18ba1ff45c3c588390744527f439060676d69a 14209a77f942ca8ceac81663456c6f68a4141202 Gitea <gitea@fake.local> 1708008748 +0100 push
14209a77f942ca8ceac81663456c6f68a4141202 41cc32246e8ec5cca67a024ad141ee54c0546f3c Gitea <gitea@fake.local> 1708594243 +0100 push
41cc32246e8ec5cca67a024ad141ee54c0546f3c 74a910fe621c445f043f96a430523b75b887f839 Gitea <gitea@fake.local> 1708594321 +0100 push
74a910fe621c445f043f96a430523b75b887f839 c70e4b68dbb7a1a452c62179ba46e1d0c4231e5f Gitea <gitea@fake.local> 1708594457 +0100 push
c70e4b68dbb7a1a452c62179ba46e1d0c4231e5f 51d5f1f0e4b6e5538eb7623b933b3bf8941e205a Gitea <gitea@fake.local> 1708594551 +0100 push
51d5f1f0e4b6e5538eb7623b933b3bf8941e205a 55e268c0e0c579e5166edb3a1588e4a0e2466d26 Gitea <gitea@fake.local> 1708594642 +0100 push
55e268c0e0c579e5166edb3a1588e4a0e2466d26 90113383003f52b370b1def725dec1e4649e379e Gitea <gitea@fake.local> 1708594685 +0100 push
90113383003f52b370b1def725dec1e4649e379e 90bba1afa06816b355b3f7e5c3b7f79c80b88e3c Gitea <gitea@fake.local> 1708595209 +0100 push
90bba1afa06816b355b3f7e5c3b7f79c80b88e3c 7ad6dc56304f95854dd7e0ae72c87e43c47c5372 Gitea <gitea@fake.local> 1708599707 +0100 push
7ad6dc56304f95854dd7e0ae72c87e43c47c5372 16a607b4e427dee7a8814949607784e1e56e749e Gitea <gitea@fake.local> 1708600318 +0100 push

View File

@ -0,0 +1,5 @@
0000000000000000000000000000000000000000 a00698f76530a28df32bde51187b91bc93507aeb Gitea <gitea@fake.local> 1707997192 +0100 push
a00698f76530a28df32bde51187b91bc93507aeb 3073e315859fc79ef9abf890640a01da87ce720a Gitea <gitea@fake.local> 1708003317 +0100 push
3073e315859fc79ef9abf890640a01da87ce720a 6f689c631f2724e454f4741c63ef2963f386154f Gitea <gitea@fake.local> 1708003388 +0100 push
6f689c631f2724e454f4741c63ef2963f386154f ecd9db8b73b30dcc9a2a2b8137e325f260a33298 Gitea <gitea@fake.local> 1708003864 +0100 push
ecd9db8b73b30dcc9a2a2b8137e325f260a33298 807da2538b9797e3880202f559bd6858a62d3e7d Gitea <gitea@fake.local> 1708005958 +0100 push

View File

@ -0,0 +1,15 @@
0000000000000000000000000000000000000000 6f08a05dcd41f7014b817fbf8d91f1b423401886 Gitea <gitea@fake.local> 1707398060 +0100 push
6f08a05dcd41f7014b817fbf8d91f1b423401886 7d89efc1909dcf24b64344fc91715a0f9195fd70 Gitea <gitea@fake.local> 1707398427 +0100 push
7d89efc1909dcf24b64344fc91715a0f9195fd70 5b65ea2912c029f55e229345710b995f1e35a9f6 Gitea <gitea@fake.local> 1707993397 +0100 push
5b65ea2912c029f55e229345710b995f1e35a9f6 20ed8ca88312f56f0623cd66ddfa070fa6a2223b Gitea <gitea@fake.local> 1707993833 +0100 push
20ed8ca88312f56f0623cd66ddfa070fa6a2223b eb18ba1ff45c3c588390744527f439060676d69a Pom <pauline@srifi.fr> 1708006008 +0100 push
eb18ba1ff45c3c588390744527f439060676d69a 14209a77f942ca8ceac81663456c6f68a4141202 Gitea <gitea@fake.local> 1708008748 +0100 push
14209a77f942ca8ceac81663456c6f68a4141202 41cc32246e8ec5cca67a024ad141ee54c0546f3c Gitea <gitea@fake.local> 1708594243 +0100 push
41cc32246e8ec5cca67a024ad141ee54c0546f3c 74a910fe621c445f043f96a430523b75b887f839 Gitea <gitea@fake.local> 1708594321 +0100 push
74a910fe621c445f043f96a430523b75b887f839 c70e4b68dbb7a1a452c62179ba46e1d0c4231e5f Gitea <gitea@fake.local> 1708594457 +0100 push
c70e4b68dbb7a1a452c62179ba46e1d0c4231e5f 51d5f1f0e4b6e5538eb7623b933b3bf8941e205a Gitea <gitea@fake.local> 1708594551 +0100 push
51d5f1f0e4b6e5538eb7623b933b3bf8941e205a 55e268c0e0c579e5166edb3a1588e4a0e2466d26 Gitea <gitea@fake.local> 1708594642 +0100 push
55e268c0e0c579e5166edb3a1588e4a0e2466d26 90113383003f52b370b1def725dec1e4649e379e Gitea <gitea@fake.local> 1708594685 +0100 push
90113383003f52b370b1def725dec1e4649e379e 90bba1afa06816b355b3f7e5c3b7f79c80b88e3c Gitea <gitea@fake.local> 1708595209 +0100 push
90bba1afa06816b355b3f7e5c3b7f79c80b88e3c 7ad6dc56304f95854dd7e0ae72c87e43c47c5372 Gitea <gitea@fake.local> 1708599707 +0100 push
7ad6dc56304f95854dd7e0ae72c87e43c47c5372 16a607b4e427dee7a8814949607784e1e56e749e Gitea <gitea@fake.local> 1708600318 +0100 push

View File

@ -0,0 +1,2 @@
x<01>ÎA
Â0@Q×9EöÌL:MD<‚à ’é Ö–˜.¼½¨7pù¾.ó<5Ow­šyR <09>䞀FÔ"0dÍ@+‰vÅ­©Ú£yÎ=["AR )ÌF$¡ãˆ<C3A3>E¸ NRz—¶v[ª¿¤í>=Ì_ëT&\<??<”zò!Š„! ß6û§uíµ.î ïC˜

View File

@ -0,0 +1,3 @@
x<01>ŽK
Â@]Ï)z/H÷tæ"=? hÆÉý<C389>z¯Š—æçsì 5îz+²¯.Ì5z&k…ƒŽyplm3hÅ1&µH+SA´as¬aísåm_ ß2S`ƒNJT²öûÜà"ëcœ
\ÛXG8.?<¿>x¨íäÐ#2“<32>=¢J߇½üã*BXäVÔÉËCá

View File

@ -0,0 +1,3 @@
x²▌K
1 @]Вы р╓Иg@д#· фuf╗УЧЧnЮР-чЦИ|©▐б╙73V.быPc U#┘аRb,∙П4╓хч2╧E M░и▓s≤T┼ hаг╓╘╕w
и⌠⌠g©л Р╪█⌠а╠█u└МРцЩЦ┐⌡зv─ы≈Ь▌╠┤╣GО²~╩ЩЦ╨G╫брФЁ{VzE2

View File

@ -0,0 +1,2 @@
x<01><>[
Β0EύΞ*ζ_<CEB6>L<EFBFBD>WAΔ%®`&<26>Π€}<7D>¦ϋΧκό<\χ¤e<C2A4>JƒρΤ<CF81><08><>yΐ,Q“<51><E2809C>Ι9K9‰η<E280B0>9t$6«•<C2AB>Μ RΠbΩΗc $λLςCΟd½ΰ “5<1D>Λ<EFBFBD>φ6.΄ΏΚ,π¬%Έ®?Όo^r½Οco<63>να¬Qk•Ύ…MώqΥΨΪΊ©7ϊFr

View File

@ -0,0 +1,3 @@
xťÎI
A @Q×uŠěIj4 âOPC v·”Ő÷ő.ßâĂŻë<O¬ő»ŃE âę|“Ş%GˇäBDŽV<C5BD>¬ŐämÔLć™»,R;˛h%FnU­/Ń;ďµ2%
•‰<E280A2>¶„&oăľv¸ćí1-·>é§çŹ—ׇíg „‰Ů9ö°GB4ő{8äźÖ4™Wč۲H7oB=F´

View File

@ -0,0 +1,3 @@
x<01><>K
Â@ @]Ï)²$i:ŸˆG<A:&8`­L§÷÷Ó¸|‹÷^ž§©4 w­ªKê»Þ'£²?Ê-P&ÏFÈbY­(Š9YÛ}®põQž
×Z¬ÀñµáyùâÁêéSÆÈCÂ.Á Ñåß±é?®³R—[½hõ9ø

View File

@ -0,0 +1,2 @@
x<01>ÎI
1@Q×9Eí©J:OP<4F>T4`ÄôýE½<45>Ë·øðÓ:ϵƒÖxèM(5¢³­ÖÖqœ´ØìÉE*ÁºÁe#Djã&KƒÞˆ!l,ÉG)‘§)sðI¼FV¼÷ÇÚàÊû³.·VK…qûñòúðTÚÈc@4&88"!ªô=ìòO«a㻨7ÉFC÷

View File

@ -0,0 +1 @@
x]<5D>K0@]÷³k‰Á<>Ÿ¤‰+¯1)R¤±Rãñ-%.°³ê|Þ¼LkC ÇËi×Çà ·jz<6A>qcˆ÷åSBÔ¾ÓI»Ñ*ÒŒ©q¹V¢WN#Œ½Íd(D|„ÙSj¨»¥Ö*†™´à^°N÷`í#Š+ƒôži»²°Í…MöšœŽšæèÿ•ÏÐj gy¹¥É )iš~Ò %pD§ŒGä«Q6ž½ÂD×]."ÏuÝ_3ãd2

View File

@ -0,0 +1,2 @@
x<01>ΞI
1@QΧ9Eν©ΚΠIƒ<49>G<A†* Ϊ1}Qoΰς->όΌLSν 5ξzc†Q“3.JCNΦDq£ΣΙ!&ƒΊ<C692>Υ>•ΤΟΑΡ•\,‰G²)<29>—$΅<>$”¬6)„AΕ­ί——Έ=λΜpmU*ΧΟ―<0F>N@½ƒΥφH<CF86>*;<3B>Σ<EFBFBD>[νζU½τΌDν

View File

@ -0,0 +1,2 @@
x<01>ÎA
Â0@Q×9Eöd™I"étŠkKšÞ_Ô¸|_y®ÝzÀCoª¶ `*„B<E2809E>(B>deFH“‡!3¡ÓèÍZš¾º%RÏIœ:¡˜•€YÇ! ”S<E280B9>Ì£gSöþXš½•ýY_jï­N՞ׯۇ§©],D—(#§`<60>œ3ò=ìúOk6ó,!B9

Some files were not shown because too many files have changed in this diff Show More