website issueshttps://foss.heptapod.net/heptapod/website/-/issues2024-01-31T18:12:54Zhttps://foss.heptapod.net/heptapod/website/-/issues/26Dead internal links in subcategory page2024-01-31T18:12:54ZGeorges RacinetDead internal links in subcategory pageThe [announcements page](https://heptapod.net/category/announcements) has wrong internal links such as `https://heptapod.net/category/heptapod-1-0-2024-roadmap.html` (`/category` instead of `/`).The [announcements page](https://heptapod.net/category/announcements) has wrong internal links such as `https://heptapod.net/category/heptapod-1-0-2024-roadmap.html` (`/category` instead of `/`).https://foss.heptapod.net/heptapod/website/-/issues/24quick-start: How to purge old/obsolete topics?2023-01-08T15:04:04ZHartmut Goebelquick-start: How to purge old/obsolete topics?When a merge-request based on one of my topics gets merged or closed, the topic still exists in my local repository.
Same for other person's topics which get pulled into my local repo.
How can I get rid of old topics? Is there some “pru...When a merge-request based on one of my topics gets merged or closed, the topic still exists in my local repository.
Same for other person's topics which get pulled into my local repo.
How can I get rid of old topics? Is there some “prune/purge topics not existing on the server” functionality?https://foss.heptapod.net/heptapod/website/-/issues/23quick-start: How to create a topic on top of another topic?2023-01-08T14:44:58ZHartmut Goebelquick-start: How to create a topic on top of another topic?Please add a short description how to create a topic on top of another topic.Please add a short description how to create a topic on top of another topic.https://foss.heptapod.net/heptapod/website/-/issues/22quick-start: Minor wording improvement2022-10-25T13:42:49ZHartmut Goebelquick-start: Minor wording improvementFor “Named branch workflow”.
In the disclaimer its unclear what “this” refers to exactly. Thus
> Disclaimer: **this** is not the workflow that we recommend …
should become
> Disclaimer: **The “named branch workflow”** is not the work...For “Named branch workflow”.
In the disclaimer its unclear what “this” refers to exactly. Thus
> Disclaimer: **this** is not the workflow that we recommend …
should become
> Disclaimer: **The “named branch workflow”** is not the workflow that we recommend …https://foss.heptapod.net/heptapod/website/-/issues/21Incorrect "Does Heptapod support both Git and Mercurial?" FAQ entry2021-11-26T12:32:48ZJ. Lewis MuirIncorrect "Does Heptapod support both Git and Mercurial?" FAQ entryI think the answer to the [Heptapod FAQ](https://heptapod.net/pages/faq.html#faq) "Does Heptapod support both Git and Mercurial?" question is out of date:
> No, but we'd love it to. If you want it sooner than later, vote for it via the ...I think the answer to the [Heptapod FAQ](https://heptapod.net/pages/faq.html#faq) "Does Heptapod support both Git and Mercurial?" question is out of date:
> No, but we'd love it to. If you want it sooner than later, vote for it via the general interest and support form.
According to the Available Now section of https://about.heptapod.host/, Heptapod supports Git:
> Heptapod has the full Git hosting capabilities of its GitLab Core foundation.
Also, the "interest and support form" link in the answer is broken (i.e., HTTP 404).https://foss.heptapod.net/heptapod/website/-/issues/20Improve "Does Heptapod have personal forks?" FAQ entry2021-11-26T12:32:48ZJ. Lewis MuirImprove "Does Heptapod have personal forks?" FAQ entryIn the [Does Heptapod have personal forks?](https://heptapod.net/pages/faq.html#forks) FAQ entry (in [content/pages/faq.rst](content/pages/faq.rst)), it says:
> Not for the time being, but we need them less than in regular GitLab.
I th...In the [Does Heptapod have personal forks?](https://heptapod.net/pages/faq.html#forks) FAQ entry (in [content/pages/faq.rst](content/pages/faq.rst)), it says:
> Not for the time being, but we need them less than in regular GitLab.
I think that statement marginalizes the value of so-called "drive-by contributions." I think drive-by contributions are very useful. At a high level, there should be no difference in the usefulness of drive-by contributions compared to GitLab, GitHub, or any other software development platform.
I would wish for that statement to be changed to something like the following:
> We acknowledge the importance of personal forks, especially for the purpose of so-called "drive-by contributions," and it's on our roadmap, but we haven't gotten to it yet.
Right now, if someone wants to contribute a typo fix or some other minor fix, they have to request to be a developer of the project, wait to be made a developer, clone, make the fix, commit, push, and make an MR. That is a huge barrier to entry making it such that I wouldn't be surprised if anyone thinking of contributing such a fix just gives up and doesn't even bother.
I understand that features have to be prioritized and that this one does not have a high enough priority to be worked on yet. I just wish that this FAQ entry would acknowledge the usefulness of being able to submit an MR without having to become a developer of the project the MR is submitted to. That is really a significant problem regardless of how it is technically implemented. To me, it has nothing to do with the recommended Heptapod workflow; I have no problem with the recommended workflow. But from a high-level functionality POV, not being able to make an MR unless you're a developer of the project you want to submit an MR to is a real problem that, IMO, seriously inhibits adoption of Heptapod as a platform.https://foss.heptapod.net/heptapod/website/-/issues/19Cannot create new project2021-05-12T17:05:29ZTimur KhuzinCannot create new project![image](/uploads/fe796317699505f09671179dab165513/image.png)
I tried to create new blank personal project on foss.heptapod.net after creation of my account but got this error all times.
I reproduced it in all visibility levels.
Also, ...![image](/uploads/fe796317699505f09671179dab165513/image.png)
I tried to create new blank personal project on foss.heptapod.net after creation of my account but got this error all times.
I reproduced it in all visibility levels.
Also, I failed to import repository too.
I tried even to change my username (assuming that namespace is my username) no luck.https://foss.heptapod.net/heptapod/website/-/issues/18Download links for Omnibus packages and Heptapod Runner2021-04-14T07:20:31ZGeorges RacinetDownload links for Omnibus packages and Heptapod RunnerNow that we have fosshost mirroring, we can publish direct links for these.Now that we have fosshost mirroring, we can publish direct links for these.https://foss.heptapod.net/heptapod/website/-/issues/17Improve the hg-evolve install instructions in the quick-start guide2021-03-07T00:03:10ZGeorges RacinetImprove the hg-evolve install instructions in the quick-start guideNowadays, there's a strong push towards the `$PYTHON -m pip` style, and it's possible to do it with a one-liner involving `hg debuginstall`, as suggested by @mforbes in [this comment](https://foss.heptapod.net/mercurial/hg-git/-/merge_re...Nowadays, there's a strong push towards the `$PYTHON -m pip` style, and it's possible to do it with a one-liner involving `hg debuginstall`, as suggested by @mforbes in [this comment](https://foss.heptapod.net/mercurial/hg-git/-/merge_requests/91#note_155563) in the context of hg-git.
Perhaps a two step approach (first we want to `pip install hg-evolve`, followed by if you want to be really sure do this…) is the best way for the reader's learning curve, or perhaps many people would be happy with a correct thing to copy-paste.
We should also document why, despite all habits in the Python development world (and my own practice for years), a direct `pip install` with no virtualenv is safe in this case.https://foss.heptapod.net/heptapod/website/-/issues/16Blog post idea : converting and keeping track of an upstream Git repo2020-09-22T11:47:40ZGeorges RacinetBlog post idea : converting and keeping track of an upstream Git repoThis is basically what we're doing for the forked Heptapod components, but it can be of use to someone else.
Extract from Mattermost chat with @burbon. All the needed info is in there, it just has to be formalized.
What is recommended/...This is basically what we're doing for the forked Heptapod components, but it can be of use to someone else.
Extract from Mattermost chat with @burbon. All the needed info is in there, it just has to be formalized.
What is recommended/correct workflow to work with git repositories? I'm using hggit. I enabled bookmarks for the repo. Locally, after it was cloned from git repo, it looks like:
```
hg:
@ changeset: 3:da91c65bc8a8
| bookmark: master
| tag: 0.0.2
| tag: default/master
| tag: tip
| parent: 0:6978c5dfd1fd
| user: superuser
| date: Mon Sep 21 21:54:30 2020 +0100
| summary: test3
|
| o changeset: 2:a98fe450e13e
|/ bookmark: test2
| tag: default/test2
| parent: 0:6978c5dfd1fd
| user: superuser
| date: Mon Sep 21 21:53:41 2020 +0100
| summary: test2
|
| o changeset: 1:8244a14a251a
|/ bookmark: test1
| tag: default/test1
| user: superuser
| date: Mon Sep 21 21:52:51 2020 +0100
| summary: test1
|
o changeset: 0:6978c5dfd1fd
tag: 0.0.1
user: superuser
date: Mon Sep 21 21:52:28 2020 +0100
summary: init
```
I'm pushing with:
```
hg push -f --new-branch
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 4 changesets with 4 changes to 1 files (+2 heads)
remote: To create a merge request for wild/8244a14a251a6b6c87ccbb9a68fd448d7ebb93a2, visit:
remote: http://Stuff/foobar/-/merge_requests/new?merge_request%5Bsource_branch%5D=wild%2F8244a14a251a6b6c87ccbb9a68fd448d7ebb93a2
remote: To create a merge request for wild/da91c65bc8a8ccba735d1553f9716342a97d302d, visit:
remote: http://Stuff/foobar/-/merge_requests/new?merge_request%5Bsource_branch%5D=wild%2Fda91c65bc8a8ccba735d1553f9716342a97d302d
remote: To create a merge request for wild/a98fe450e13e58fd6c1ef5728221439a342e9ad4, visit:
remote: http://Stuff/foobar/-/merge_requests/new?merge_request%5Bsource_branch%5D=wild%2Fa98fe450e13e58fd6c1ef5728221439a342e9ad4
```
What do i do to get those wild branches named after hg bookmarks/git branches? The only branch with actual name that gets created is default. (edited)
Tue, Sep 22, 2020 Georges Racinet 10:37 AM
What happens is that you're not pushing the bookmarks. If you do hg push -fB master, hg push -fB test1 etc, it should work, and the "wild" GitLab branches will be removed
Błażej Cegiełka 12:44 PM
And what do you do with git tags? i have them in hg-git converted repo, but they are not looking pushed into heptapod - they don't show up in UI, and no tags are present when project is hg-cloned from heptapod.
Georges Racinet 1:05 PM
@burbon hg-git puts the Git tags in .hg/git-tags and has the related code so that hg tags displays them, but they aren't pushed
what I'm doing to include them in regular hg tags is to actually commit them in .hgtags but I don't want to introduce new commits on top of the ones converted from Git (would break subsequent conversions)
so what I'm doing, is that I started a dedicated (named) branch, actually a new root of the repo, something like
```
hg up 000000000000
hg branch git-tags
cp .hg/git-tags .hgtags
hg add .hgtags
hg ci -m "Imported Git tags as Mercurial tags"
```
and then, each time I make a new import, I commit that file again in the dedicated branch. What matters for Mercurial tags system is the content of .hgtags in any absolute repository head.
you can see this here: https://foss.heptapod.net/heptapod/heptapod/-/network/branch%2Fgit-tags and here: https://foss.heptapod.net/heptapod/heptapod/-/tree/branch/git-tagshttps://foss.heptapod.net/heptapod/website/-/issues/15Blog post authors don't get displayed2020-09-22T11:36:41ZGeorges RacinetBlog post authors don't get displayedThere are many reasons for blog posts (not announcements) to have a visible author besides giving credit where it's due.
For instance, it allows for a more relaxed way of posting, such as writing in the first person of the singular, open...There are many reasons for blog posts (not announcements) to have a visible author besides giving credit where it's due.
For instance, it allows for a more relaxed way of posting, such as writing in the first person of the singular, opening the possibility for readers to know whom to ask questions etc.
But currently even though our blog posts have author metadata, be it in Markdown or in reStructuredText, they don't get displayed.
It's possible that it'd be to be fixed in the theme.https://foss.heptapod.net/heptapod/website/-/issues/14Unable to push repo with Multiple Heads with `single-head-per-branch = no` [E...2020-06-18T16:13:14ZEddy FUnable to push repo with Multiple Heads with `single-head-per-branch = no` [Evolve Topics]Please feel free to close the issue if you need me to submit as a support ticket instead!
**Background:**
We're currently using evolve topics, thus in need of multiple heads. As we're trying to migrate from Bitbucket to Heptapod, we're...Please feel free to close the issue if you need me to submit as a support ticket instead!
**Background:**
We're currently using evolve topics, thus in need of multiple heads. As we're trying to migrate from Bitbucket to Heptapod, we're noticing a few issues.
**Repro steps:**
1. Set `single-head-per-branch = no` via PUT API request according to docs.
2. Confirm that change was made in server `hgrc` settings via GET request.
3. Push to remote repo.
4. Push fails with `remote: push create more than 1 head on new branch "default"`
-----------
On another note, when using `--force` or `--new-branch` flag, the repo ends up with multiple `wild/****` branches as expected, and also `default/topics/<topic_name>` branches that are marked as `public` phase when they should be in `draft` phase.
![Screen_Shot_2020-06-17_at_08.51.15](/uploads/077a672e99180611613faf587f0a096e/Screen_Shot_2020-06-17_at_08.51.15.png)
Also my understanding is that `push` changes the remote phases thus also affects local repo phase data..
In our use case, we end up having to strip out local topics manually and pull from bitbucket default repo to restore the phase data.
https://foss.heptapod.net/heptapod/website/-/issues/13Document REST API endpoint to allow multiple heads2020-06-18T01:59:19ZEddy FDocument REST API endpoint to allow multiple headsUse case:
`hg-evolve extensions` repors need multiple heads / branch support.
We need to be able to set
```[experimental]
single-head-per-branch = no
```
server-sideUse case:
`hg-evolve extensions` repors need multiple heads / branch support.
We need to be able to set
```[experimental]
single-head-per-branch = no
```
server-sidehttps://foss.heptapod.net/heptapod/website/-/issues/12The website is not responsive?2020-06-15T14:54:51ZPierre AugierThe website is not responsive?The width of the page does not adapt to small screens (at least on mine phone, which is running UBports).
Note : same with https://octobus.net/The width of the page does not adapt to small screens (at least on mine phone, which is running UBports).
Note : same with https://octobus.net/https://foss.heptapod.net/heptapod/website/-/issues/11example.com address shown on Mattermost first-login flow2020-06-03T19:47:32ZAndi McClureexample.com address shown on Mattermost first-login flowToday I signed up with your Mattermost server. The first time I logged in (that is, the first time I clicked "Sign in with Gitlab" here:)
![Screen_Shot_2020-06-03_at_3.27.20_PM](/uploads/3399d2c12e0356362223e3a16bad18f9/Screen_Shot_2020...Today I signed up with your Mattermost server. The first time I logged in (that is, the first time I clicked "Sign in with Gitlab" here:)
![Screen_Shot_2020-06-03_at_3.27.20_PM](/uploads/3399d2c12e0356362223e3a16bad18f9/Screen_Shot_2020-06-03_at_3.27.20_PM.png)
It showed me a one-time message containing instructions to email webmaster@example.com if anything went wrong. Probably there is a default set somewhere and you want to change it.
I unfortunately do not have a screenshot. It appears the message only appears once and to make it appear again I would have to make a second Heptapod account.https://foss.heptapod.net/heptapod/website/-/issues/10Mattermost login process is unclear2020-07-10T12:33:39ZAndi McClureMattermost login process is unclearLet's say I am a new user to Heptapod (as I was this morning) and I wanted to find something like a support forum. There is a big "Contact" button on the front page of Heptapod so I click that. I get [this page](https://heptapod.net/page...Let's say I am a new user to Heptapod (as I was this morning) and I wanted to find something like a support forum. There is a big "Contact" button on the front page of Heptapod so I click that. I get [this page](https://heptapod.net/pages/contact-us.html#contact-us):
![Screen_Shot_2020-06-03_at_3.27.07_PM](/uploads/e2e2fa0cc39d62d14390b1f3f03bc0ea/Screen_Shot_2020-06-03_at_3.27.07_PM.png)
**These instructions are misleading.** If I click "User Support Mattermost Channel", I get this login page:
![Screen_Shot_2020-06-03_at_3.27.20_PM](/uploads/02710a4525b8e74fc7bee140a4b11522/Screen_Shot_2020-06-03_at_3.27.20_PM.png)
The correct thing to do here is ignore the user/password login and click "Sign in with Gitlab". However, as a new user, I could not figure this out. I assumed "Sign in with Gitlab" meant signing in with a Gitlab.com account. I wasted some time looking at other pages and wound up creating a Gitlab.com account just to log in (unnecessarily it turns out).
Georges Racinet told me on your Mattermost that right now you cannot alter the "Sign in with Gitlab" page. So I think my **expected behavior** is, you should change the "Contact" page so that users do not get confused by the instructions. My suggested text is:
* register on our own Heptapod instance, then start the conversation on the User Support Mattermost channel by clicking the "sign in with GitLab" buttonhttps://foss.heptapod.net/heptapod/website/-/issues/9FAQ: how to launch `hg` in the Docker container2020-07-13T09:50:35ZGeorges RacinetFAQ: how to launch `hg` in the Docker containerIt's a recurring question, should be added as a FAQ item.
It's crucial to have the proper user and configuration, with
something like (from memory, untested):
```
su git -s /bin/bash
HGRCPATH=/etc/gitlab/heptapod.hgrc:/opt/gitlab/etc/d...It's a recurring question, should be added as a FAQ item.
It's crucial to have the proper user and configuration, with
something like (from memory, untested):
```
su git -s /bin/bash
HGRCPATH=/etc/gitlab/heptapod.hgrc:/opt/gitlab/etc/docker.hgrc hg …
```https://foss.heptapod.net/heptapod/website/-/issues/8Tutorial: HTTPS push/pull with personal token2020-06-03T15:00:46ZGeorges RacinetTutorial: HTTPS push/pull with personal tokenThat's been on my mind for a while.
It's necessary for instances without password authentication (notably https://heptapod.host) and for users with two factor authentication (2FA)That's been on my mind for a while.
It's necessary for instances without password authentication (notably https://heptapod.host) and for users with two factor authentication (2FA)https://foss.heptapod.net/heptapod/website/-/issues/7Fix links without anchor2020-05-25T12:56:40ZGeorges RacinetFix links without anchorWith the Flex theme we're using, on smart phones, internal links without anchor have the effect to scroll up to the general menu (takes a full screen).
This is cumbersome if coming from another page, and makes the viewer believe the lin...With the Flex theme we're using, on smart phones, internal links without anchor have the effect to scroll up to the general menu (takes a full screen).
This is cumbersome if coming from another page, and makes the viewer believe the link is inert if coming from the menu (no visible change).
There are currently several such links and even one in the menu.https://foss.heptapod.net/heptapod/website/-/issues/6front page update2020-04-18T16:48:07ZPierre-Yves Davidfront page updateThe landing page of https://heptapod.net/ has not been updated for a while.
It think it would be useful to do some of the following:
* [x] update de status of the project,
* [x] point at the Free software hosting option,
* [x] point at...The landing page of https://heptapod.net/ has not been updated for a while.
It think it would be useful to do some of the following:
* [x] update de status of the project,
* [x] point at the Free software hosting option,
* [x] point at the Commercial hosting option,
* [x] point at the self hosting option,
* [x] link to the most important tutorials.
* [x] link to more up to date ressource (eg: fosdem video),
(Whoever does this should take the abovel list as an inspiration, not a strict task list. I ordered it from what I felt most important to least important.)Georges RacinetGeorges Racinet