My understanding is that at the moment commits are restricted to what’s I the designated src directory, so you need to use an external way to commit non code files into your branch. These can be 1. Git cmd line 2. Another tool like IntelliJ 3. The github web bowser
If you do, you need to pull or merge in Pharo to keep things in sync. I also hope one day we might widen the scope to commit more things directly in Pharo - particularly the readme ir other config files (I gave the same problem with exercism ) Tim Sent from my iPhone > On 6 Apr 2019, at 22:45, Christopher Fuhrman <christopher.fuhr...@gmail.com> > wrote: > > Hi Konrad, > >> On Sat, 6 Apr 2019 at 15:46, Konrad Hinsen <konrad.hin...@fastmail.net> >> wrote: >> Hi everyone, >> >> Is it possible to read and modify files not containing Pharo code in a >> repository managed by Iceberg? I am thinking of reading the repository's >> README file, for example, or storing data files read by my code >> alongside the code itself. > > I'm not sure if you are referring to GitHub's README, but if you are, I > maintain my project's README on GitHub's web site (which requires care if > you're using branches). I like the markdown preview there which requires no > fancy software installed on my PC. You need to pull the change to Iceberg. > > There's indeed a copy of the README.md in my image's > pharo-local/iceberg/GITHUBUSERNAME/GITHUBPROJECT directory, and I can even > modify it using Pharo 7's File Browser. However, any modifications to it are > not seen or committed by Iceberg (at least I don't know of a way to make that > happen). I believe Iceberg's change detection is limited to the smalltalk > files in the packages that are in the repositories it knows about. But I'm > still far from an expert with this. Hopefully a more qualified person can > confirm. > > There's theoretically a way to run a git client outside of Pharo that knows > about the local git repo that Iceberg's using, so maybe you can commit the > non-Pharo files that way. However, doing that is sure to cause a "detached" > state with the repo in the image. That is not a catastrophic problem, but > it's more accidental complexity to deal with. I picked my battles and > maintain README on GitHub. > > Christopher > >> >> Konrad. >> > > > -- > Christopher Fuhrman, P.Eng, PhD > Professor in the Département of Software and IT Engineering > ÉTS (École de technologie supérieure) > > http://profs.etsmtl.ca/cfuhrman > +1 514 396 8638 > L'ÉTS est une constituante de l'Université du Québec > Confidentiality Notice > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. If > you have received this email in error please notify > christopher.fuhr...@etsmtl.ca. This message contains confidential information > and is intended only for the individual named. If you are not the named > addressee you should not disseminate, distribute or copy this e-mail. > Avis de confidentialité > L'information contenue dans ce message électronique ainsi que dans les > fichiers qui peuvent y être attachés est de nature confidentielle et destinée > à l'usage exclusif du destinataire. Si ce message vous est parvenu par erreur > ou que vous n'êtes pas le destinataire visé, vous êtes par la présente avisé > que tout usage, copie ou distribution de l'information contenue dans ce > message est strictement interdit et vous êtes prié d'en aviser > christopher.fuhr...@etsmtl.ca et de détruire ce message.
