# Contribution mechanism in Nest

**URL:** <https://discourse.pijul.org/t/contribution-mechanism-in-nest/848>\
**Category:** Question\
**Created:** [January 20, 2022, 7:31pm UTC](https://discourse.pijul.org/t/contribution-mechanism-in-nest/848 "2022-01-20T19:31:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![HKalbasi](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/hkalbasi/32/420_2.png) [@HKalbasi](https://discourse.pijul.org/u/HKalbasi)\
**Post date:** [January 20, 2022, 7:31pm UTC](https://discourse.pijul.org/t/contribution-mechanism-in-nest/848/1 "2022-01-20T19:31:23Z")

</div>

Sorry if it is an obvious question, but I don’t see the equivalent of fork/pull request of github in Nest. Is it exists? If not, is it planned? Would it have the same form of github, or something completely different? And what is the current way of contribution to the repositories on the Nest? Email?

---

<div class="post-metadata">

**Author:** ![pmeunier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pmeunier/32/4_2.png) [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Post date:** [January 20, 2022, 10:10pm UTC](https://discourse.pijul.org/t/contribution-mechanism-in-nest/848/2 "2022-01-20T22:10:53Z")

</div>

It exists, and I find it better than pull requests: you can attach loose patches to discussions, by pushing them to a special channel whose name is the discussion number.

Since these (fake) channels are always empty, you probably want to compare them with `main`, which you can do with `pijul push --to-channel main:65` (for discussion number 65), or simply `pijul push --to-channel :65` since `main` is the default channel.

---

<div class="post-metadata">

**Author:** ![yin](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/yin/32/517_2.png) [@yin](https://discourse.pijul.org/u/yin)\
**Post date:** [April 25, 2023, 6:13am UTC](https://discourse.pijul.org/t/contribution-mechanism-in-nest/848/3 "2023-04-25T06:13:53Z")

</div>

```auto
$ pijul log --limit 3
Change PVKZGUAQJ36VYQBFXZTFWRAZBPF2C4HA2GHYNIKANIDYQHS6JMEAC
Author: yin (yin) <yinotaurus@gmail.com>
Date: Tue, 25 Apr 2023 06:11:17 +0000

    Spellcheck and simple language editing: `installing.md`

Change 4DFTUSDYMW7IKJON7IRXU5H5VRW2OPRANOEGL3OUTQMLNMZ6GKQAC
Author: yin (yin) <yinotaurus@gmail.com>
Date: Tue, 18 Apr 2023 00:09:20 +0000

    Spellcheck and simple language editing: `why_pijul.md`

Change WLSTU64AZ2B26WTWJWQ3HKS6PGYYHZCCFP5PLYQXGNUH4IIW5EUQC
Author: FZQ2g7VfnzLYM4mtTVDk9HAZjA8Jk9ndkwN1icgbtWUr
Date: Fri, 08 Apr 2022 13:16:55 +0000

    Fixing the script that generates the reference from CLI options

$ pijul remote
  IFAUCQKBIFAUCQKBIFAUCQKFIE: https://nest.pijul.com/pijul/manual

$ pijul push --to-channel :57
Uploading changes [>] 0/2                                                                           
Error: The HTTP server returned an error: No command specified

```

How would I approach debugging this error message? I don’t see how to pass debug flags here.

---

<div class="post-metadata">

**Author:** ![pmeunier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pmeunier/32/4_2.png) [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Post date:** [April 25, 2023, 6:54am UTC](https://discourse.pijul.org/t/contribution-mechanism-in-nest/848/4 "2023-04-25T06:54:17Z")

</div>

The Nest is being rewritten, we’ll soon have a new shiny open source serverless Nest without these error messages.

Meanwhile, the only way to send changes is via SSH:

`pijul push yin@ssh.pijul.com:pijul/manual --to-channel :57`

You can edit `.pijul/config` in your repo to make the remote the default. Since I guess you cloned from HTTP the default is probably set to that.

---

<div class="post-metadata">

**Author:** ![yin](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/yin/32/517_2.png) [@yin](https://discourse.pijul.org/u/yin)\
**Post date:** [April 25, 2023, 8:37pm UTC](https://discourse.pijul.org/t/contribution-mechanism-in-nest/848/5 "2023-04-25T20:37:36Z")

</div>

Thank you, that worked.

Let’s wait for the awesome new Nest then…

My feedback so far, just for giggles, 2 issues I had:

- The intended clone/push path was not totally smooth. I previously tried to clone a repo using SSH, but the correct ssh address was not advertised on the Nest project (I just took the HTTPS url).

- Another face of the previous issue is, that I was not able to figure out the SSH url just from reading the documentation. I had some expectation about the SSH url from using Git…

- The repo set up and setting up the identity was a bit confusing - I wonder, whether anyone else is taking notes on improving documentation - I can share mine to compare.