You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: stack/adding-a-new-package.rst
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ Adding a New Package to the Build
7
7
Creating a new package
8
8
======================
9
9
10
-
To create a new LSST package, send a "create project" message to ``@sqrbot-jr`` on the LSST Slack and select "LSST EUPS package" as the project type.
10
+
To create a new LSST package, send a "create project" message to ``@squarebot`` on the LSST Slack and select "LSST EUPS package" as the project type.
11
11
Follow the prompts to select the GitHub organization (choose ``lsst`` for the `LSST organization on GitHub`_ for packages that you plan to add to the full distribution via RFC, as described below) and the specific flavor of package (e.g. ``Pipelines Python`` for a typical python package that depends on `pipe_base`_) to get an appropriate directory structure set up.
12
12
The bot uses the templates in the `lsst/templates`_ repository to define the package layout.
13
13
@@ -99,8 +99,8 @@ Configuring GitHub Repositories
99
99
100
100
.. Note::
101
101
102
-
If you created your package via ``@sqrbot-jr`` on the LSST slack, the GitHub repo should be configured correctly.
103
-
These instructions are for the rare cases that cannot be handled by ``@sqrbot-jr``.
102
+
If you created your package via ``@squarebot`` on the LSST slack, the GitHub repo should be configured correctly.
103
+
These instructions are for the rare cases that cannot be handled by ``@squarebot``.
104
104
105
105
All LSST DM repositories on GitHub must be configured by a repository administrator to protect the ``main`` branch and to ensure that the merge button for pull requests can not be pushed without the branch being up to date with ``main``.
106
106
There are a number of settings required to ensure this and they are described below with URLs referring to the ``afw`` package.
@@ -145,7 +145,7 @@ Handling Git LFS-backed repos
145
145
=============================
146
146
147
147
New :doc:`Git LFS-backed </git/git-lfs>` repos (or existing repos being converted to LFS) require additional configuration.
148
-
``@sqrbot-jr`` cannot yet create an empty LFS-ready repo.
148
+
``@squarebot`` cannot yet create an empty LFS-ready repo.
149
149
150
150
- The `repos.yaml`_ entry must declare that the repository is LFS backed:
0 commit comments